By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,940 Members | 611 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,940 IT Pros & Developers. It's quick & easy.

Automation Error -- Library not registered.

P: 16
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\ado\msadox.dll"
Doesn't help. The same module is working well on my laptop, not affected by installation any new software.
Any suggestions?
Feb 9 '09 #1
Share this Question
Share on Google+
16 Replies


puppydogbuddy
Expert 100+
P: 1,923
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.
Feb 9 '09 #2

P: 16
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("Scripting.FileSystemObject")
...
fs.CreateFolder (path)
...
Feb 9 '09 #3

puppydogbuddy
Expert 100+
P: 1,923
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.
Feb 9 '09 #4

P: 16
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
Feb 9 '09 #5

puppydogbuddy
Expert 100+
P: 1,923
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.
Feb 9 '09 #6

P: 16
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.
Feb 9 '09 #7

puppydogbuddy
Expert 100+
P: 1,923
From what you have said, no references are missing, but you are gettng a registraton error when you reference the file scripting object....implying that you need to register a dll using regsrvr32. Are you using an activeX frrom a third party?
Feb 9 '09 #8

FishVal
Expert 2.5K+
P: 2,653
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.
Feb 9 '09 #9

P: 16
No. As I said already, I was registering msadox.dll, didn't help.
Feb 9 '09 #10

puppydogbuddy
Expert 100+
P: 1,923
If sas is a 3rd party activeX, you probably need to register it using your windows os regsrvr32.
Feb 9 '09 #11

FishVal
Expert 2.5K+
P: 2,653
@FelixS
I don't think msadox.dll is an issue, try to reregister scrrun.dll.
Feb 9 '09 #12

P: 16
scrrun.dll: Search returns no results on my PC C:\
Feb 9 '09 #13

FishVal
Expert 2.5K+
P: 2,653
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.
Feb 9 '09 #14

P: 16
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. "
Feb 11 '09 #15

FishVal
Expert 2.5K+
P: 2,653
Hellow Felix.

That means there is no Microsoft Scripting Runtime library registered and taking into account post #13 there is no correspondent dll at all (at least with a name it exists in Win XP). I don't have an answer as for when and why it has been lost. :)

So, download scrrun.dll (here for example) and register it with regsrvr32.

Regards,
Fish.
Feb 11 '09 #16

P: 16
Dear Fish, Your last recommendation has solved the problem!.
Thank you very much. Now it works as expected.
Feb 11 '09 #17

Post your reply

Sign in to post your reply or Sign up for a free account.