CAUSE
This error occurs because many of the MSDN code examples use late binding to the Microsoft Scripting Runtime (the component that contains the FS0.) Because late binding is used, a reference to the component (Scrrun.dll) is not required. When you use the Setup Wizard or Package and Deployment Wizard to package your application, the Wizards look at the references in the project to see which components need to be included in the package. Because there is no reference for this component, the component is not included, and the end result is an error when you attempt to create an FSO. (FSO is File System Object, its a windows object that allows reading and writing to the windows file system)
This problem is not specific to the FSO or the Scripting Runtime. The error can occur with any component when you use late binding. If you are using late binding, make certain that the component you are late binding to is either included with your application package or is already present on the target computer. (The Database object uses Late Binding in GarrettLoader, but the Scrrun.dll was not included in the install package (my mistake) this will be done for the next release).
RESOLUTION
The Microsoft Scripting Runtime must be installed from the Microsoft Windows Script components. The Microsoft Windows Script components are installed by a self-extracting EXE. You can redistribute this EXE with your setup package. Alternately, your customers can download and install the appropriate self-extracting EXE at following Microsoft Web site:
(http://www.microsoft.com/downloads/details.aspx?FamilyID=01592C48-207D-4BE1-8A76-1C4099D7BBB9&displaylang=en)

CAUSE
There are some general Office 2000 SR-1 issues that have been tracked down to the scenario of a Microsoft Windows NT 4.0-based computer running Office 2000, updating the system to Microsoft Windows 2000, and then updating to Office 2000 SR-1.
The issue with DAO described in the "Symptoms" section is one these issues. Specifically, it affects DAO registry entries related to the design-time license key.
RESOLUTION
Download the Microsoft Office 2000/Windows 2000 Registry Repair Utility. The Microsoft Office 2000/Windows 2000 Registry Repair Utility restores the registry settings for several important files that prevent potential issues.
The following file is available for download from the Microsoft Download Center. Click the file name below to download the file:
(http://download.microsoft.com/download/office2000pro/o9regfix/2000/win98/en-us/o9regfix.exe)

The class isn't registered. For example, the system registry has no mention of the class, or the class is mentioned, but specifies either a file of the wrong type or a file that can't be found.
If possible, try to start the object's application (MS Access In this case if you have it). If the registry information is out of date or wrong, the application should check the registry and correct the information. If starting the application doesn't fix the problem, rerun the application's setup program.

A DLL required by the object can't be used, either because it can't be found, or it was found but was corrupted.
Make sure all associated DLLs are available. For example, the Data Access Object (DAO) requires supporting DLLs that vary among platforms. You may have to rerun the setup program for such an object if that is what is causing this error. (possibly the Scrrun.dll in this case)

If the attempt to instantiate is the result of a CreateObject or GetObject call, the object must find the key. In this case, it may search the system registry or look for a special file that it creates when it is installed, for example, one with the extension .lic. If the key can't be found, the object can't be instantiated. If an end user has improperly set up the object's application, inadvertently deleted a necessary file, or changed the system registry, the object may not be able to find its key. If the key can't be found, the object can't be instantiated. In this case, the instantiation may work on the developer's system, but not on the user's system. It may be necessary for the user to reinstall the licensed object. (This is possible but unlikely)

Access to the object has explicitly been denied.
For example, you may be trying to access a data object that's currently being used and is locked to prevent deadlock situations. If that's the case, you may be able to access the object at another time. (This is also possible and may be due to the GarrettLoader program folder being read only for some reason).