Read this article for step-by-step instructions on how to easily add the
VBScript samples files available from the Microsoft TechNet Script Center
to your disk and integrate them in the OnScript Editor as a Script Library.
 

Download and unpack the Do-It-Yourself Kit to a folder on your machine. If you don’t already have the do_it_yourself_kit.exe file, you can find it in the “Prerequisites” section at the end of this page.

In this example I unpacked it to “C:\Program Files\Microsoft Scripting Tools”.

The EXE will unpack a bunch of files to the folder you specified. For the purpose of these instructions we are interested in the Access Database script_center_2.mdb and the first two VBScript files.

Feel free to browse the documentation and other script files to get an idea of further possibilities offered by the Do-It-Yourself Kit.

The scripts we will run to generate the sample files are not very flexible and will do exactly two things: create a folder structure beneath C:\Code and generate VBScript files in the subfolders.

To keep things simple, this is all we cover in these instructions. If you want the folder structure and files to be stored somewhere else or are interested in other script files types such as JScript, Perl, Python and others then take a look at the document called “Creating a Set of Stand-Alone Scripts”. You will have to apply some simple changes to the scripts we use here.

Create a Folder called Code in the root of the C: drive.

Then, from within Windows Explorer, run the code_folder_maker.vbs script. It won’t bother telling you when it is done or anything, but it runs rather fast. Now you should see the folders it created in C:\Code:

If you are curious, expand the complete folder structure (press *) to check the subfolders the script just created:

Next, run the code_maker.vbs script (also from within Windows Explorer). This is the script that generates the actual script files and it runs a minute or longer. While it does not really give you an indication of progress, you can see it accesses the Access Database file because a temporary LDB file suddenly appears:

As soon as the script is done, the LDB file disappears and you should be able to see some VBScript files in any of the leaf folders (lowest):

Enter the library name (this is how our new content will appear on the Library tab). In the example below I called it “Script Center Samples”.

Then, set the Library path by browsing for C:\Code:

This is what the Library Properties looked like after I did this:

Now you're all set...