Automation Error -- Library not registered.

[FelixS]

I have running one application (.mde file) of MS access 2003, quite a long time on Windows XP, - it was working well. Recently on my PC was installed SAS, after that while running my .mde application I am getting message
"Automation Error -- Library not registered".
I have found in WEB one recommendation - register module msadox.dll.
Regsvr32.exe "C:\Program Files\Common Files\System\ad o\msadox.dll"
Doesn't help. The same module is working well on my laptop, not affected by installation any new software.
Any suggestions?

[puppydogbuddy]

You need to check for missing references in your Access vb library. To do this place any of your forms in design view and go to the code editor. Once you are in the Code view, go to the Access command menu, and select Tools> References, checking for any missing references.

[FelixS]

Well, How I know which library is not connected (referenced). Usually there are only 5-6 out of many available.In fact, I have found already that error occurs while creating new folder by
Set fs = CreateObject("S cripting.FileSy stemObject")
...
fs.CreateFolder (path)
...

[puppydogbuddy]

when you open up the references library it will tell you which one (if any) are missing. You will see the words Missing beside the missing library reference.

[FelixS]

In my version of MS Visual Basic, when I go to Tools->References I see the Box with names of libraries and box for ticking before each name. No "MISSING" words. In the list of available references now there are 5 ticked ones, The others are empty. First of all, I think, this was also before it happens. Besides, I have no idea, what another library I need

[puppydogbuddy]

I just realized that you are looking at your mde file which has the code stripped out. You need to use your mdb file to determine which file is missing. In order to make a determination using an mde file, you would have to embed reference checking code behind a module that you could call from a button on a form.

[FelixS]

no - no -no. I am exercising with *.mdb original file. Ones more, when copying it to another machine, where SAS is not installed, I can observe it working as expected.

[puppydogbuddy]

From what you have said, no references are missing, but you are gettng a registraton error when you reference the file scripting object....imply ing that you need to register a dll using regsrvr32. Are you using an activeX frrom a third party?

[FishVal]

It doesn't look like a problem with library referencing.
It looks like a problem with:

• Library registration. Try to reregister scrrun.dll
• Antivirus software blocking scripting commands (e.g. Kaspersky Office suit is known to do it). Try to temporarily disable antivirus and antimalware software.

[FelixS]

No. As I said already, I was registering msadox.dll, didn't help.

[puppydogbuddy]

If sas is a 3rd party activeX, you probably need to register it using your windows os regsrvr32.

[FishVal]

No. As I said already, I was registering msadox.dll, didn't help.

I don't think msadox.dll is an issue, try to reregister scrrun.dll.

[FelixS]

scrrun.dll: Search returns no results on my PC C:\

[FishVal]

Try to search registry HKCR\CLSID for subkey with "Scripting" in a case your library has other name.

Or better search registry for "Microsoft Scripting Runtime" or try to reference it from VBA editor and then find path to the dll.

[FelixS]

1. Status for now: Problem is not solved.
2. Suspicion that installation of SAS principally causes this problem has not confirmed, since on the other PC in the unit SAS and MS access are working well together, the module in quesion has been copied there and tested.
3. I can't catch the step-by-step actions to test the last suggestion:
<<Or better search registry for "Microsoft Scripting Runtime" or try to reference it from VBA editor and then find path to the dll.>>
since the "find" in registry with "Microsoft Scripting Runtime" returns nothing, in VBA reference box there is no library with that name, and if there were, How to "...then find path to the dll. "