Error in loading dll

[Guest_imported]

Newbie need urgent help here. I've just installed the application proxy of my server dll to another client machine ,which has just upgraded from Win 98 to Win 2000, through the component services and follwed by the installation of the client program. Everything is being installed successfully but when I start the client application, the following error message appeared, "Run time error '48':Error in loading dll" and strangely despite the error, the related com services on the server machine would start operation normally.

I have the suspicion that this error is caused by incorrect placing of the systems files during the client program installation in the directory, C:windows/system32 instead of C:winnt/system32 as the upgrade of the client machine to windows 2000 did not rename the "windows" folder to "winnt". Can anybody enligthen me on this problem? Thanks in advance.

 

[SemperFiDownUnda]

Not sure I fully follow you but where your proxy DLLs reside make little difference. If you installed the proxies on the client machine then upgraded the fact that the DLL's didn't move makes no difference as the registry (that should have been brought over) will still have the same location. But to be safe just re-export the packages and run the MSI(s) on the client machine agian.

 

[Guest_imported]

I apologise for not stating my problem clearly. What I want to know what would have cause the "Error in loading dll" message? Is the the client application itself or the application proxy?

 

[SemperFiDownUnda]

Error loading dll is generated by the client application.

Disregarding ActiveX DLLs a program has a list of DLL's that it needs loaded by name. In the terms of ActiveX it goes through a intermediate step of looking up the GUID it has for the component and attempts to load DLL as it is registered with the system. I guess a component could generate a similar error if it loads or uses DLL's also.

I would have thought your program would have not run if it got this error so maybe it is some type of DLL version problem that your program may or may not encounter (crash) depending on what you use.

Sorry, your explanation isn't bad as much as I'm pretty ill at the moment and only have about 10% of my metal powers it seems.

 

[Guest_imported]

Thanks for the great tip SemperFiDownUnda. I've finally got my client app working after manually installed the Microsoft Data Access components 2.7 RTM. Guess the dll error is being caused by the Microsoft Activex Data Objects 2.7 library dll. I think the MDAC I've exported previously is an outdated one thus causing the error.