Software

Ask something
Question Locked

Error in loading .dll

0 helpful
4 replies

by omnknt232006 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am building this Access 2003 DB but am having difficulties. The DB runs fine on my machine however if I try to open it on any other machine it won't open and it gives me the error - Error in Loading dll. I did some research and it suggested that one of my DLL files is missing on the other computer however I haven't used any dll files when I have been building the DB so I think it is one of MS Access's DLL's. I did a search with the built in XP search to find all the DLL's in the MS Office folder with in my computer and did the same on the other computer and am unable to find a DLL that my computer has that the other computer doesn't have. We are both running MS Access 2003 with SP3 and also both have the hotfix that came out a couple of weeks ago, and both computer's have same build number (11.8204.8221). Does anybody else have any other ideas?

4 replies

by mickey6

1) PATHs
7 years ago i was brought on to an Access project that 4 consultants tried and couldn't fix.

While this was a network shared DB every time someone not on the host PC tried to open the DB it couldn't find the dubordinate DB files.

When I looked into it i found the macros were using absolute paths to files instead of relative paths so the host could find them but no-one else.

I simply exported the data, macros as text files and all views, started a new DB project, then imported the data and views. I then edited out all absolute paths in the macros and imported them.... Wala it fixed the issues.

2) DLL REGISTRATION
I have on more than one occation seen MS copy DLLs in the install process but fail to register them.

You can use the REGSVR32 program to register / deregister them again if needed.

Access copies several DLLs to the c:\windows\systen32 directory. These will be in your system PATH.

a simple;
REGSVR32
NOTE: full path may be needed if the DLL's directory is not in your system PATH variable.

http://www.ss64.com/nt/regsvr32.html is an excelent description of its use and all options.

Hope one of these works.

and a Merry Christmas

by omnknt232006

Thanks so much for both of these suggestions, I tried them both but still have not had any success. I think we're going to try uninstalling and reinstalling Office 2003 on the user's computer next. I'm finding this to be similar to tying to find a needle in a haystack. Thanks again.

by omnknt232006

Upon closer inspection, I checked the reference libraries in the VB Module and found out that the DB was referencing Excel 2007 while the users only had Excel 2003. I discovered this by going into the code of any of the vb in the app and clicking the tools menu -> references-> and seeing the libraries it referenced. My research also indicated you can fix this problem differently by doing something called late binding which is WAY over my head as far a programming goes. Also, I didn't have to go back to using Excel 2003 because 2007 is backwards compatible. I hope this helps all the people out there who encounter this error in the future.

This discussion is closed to new replies.