"dll hell" Resolution

[llkhoutx]

I have a Win98 PC which has 3 versions of Access loaded; 97, 2000 & XP. Periodically, I have to reformat the hard-drive reload the operating system and reload all the software. Last week I had to do it again.

Usually this is accomplished with no problems. On my recent reload of Access 2000 & 2002, DAO360.dll didn't get registered (i.e. loaded).

I searched and searched, for days, until I finally found Article Q310803

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q310803

in Microsoft's Knowdlege Base.

It has specific instructions for finding and registering dlls that don't get registered/loaded.

In a nutshell, locate file regsvr32.exe on you system, then run that program with its full path in the Start|Run Window as follows:

c:\the path to the file\regsvr32.exe /s dao360.dll

and voila, you're in business.

Maybe this will save a few of you from the grief I've suffered.

 

[fuzzygeek]

Been there

I had the problem back with Access 97 about 5 years ago and found the following site:

http://www.mvps.org/access/bugs/bugs0007.htm

Another problem that came up was that a customer kept getting errors with every database that I sent them. Their references were correct but they got ado errors. I stripped all ado out (except that which was inherent in a switchboard). Finally, out of exasperation, I had them run the Microsoft Component Checker on their system. Every one of their ado dll's were corrupt. I recommended that they remove office and reload. The Component Checker is described in the following hyperlink with a link to it's download site:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmdac/html/data_mdacinstall.asp