tags:

views:

23

answers:

2

If the above error is shown during the execution of a VB6 app, is the solution to re-register DLLs that it might be accessing at the time?

Or is this an issue about versions of DLLs not being correct?

A: 

I've seen this error before with controls (ocx). It can usually be solved by recompiling the program with the latest version.

If that's not the issue, I find a good brute-force method to clean the registry and check you have the correct version installed is to simply delete the dll in question (or just rename it) and then use a utility like CClean to delete the orphaned entry. I admit it's a sledgehammer to crack a nut.

pm_2
A: 

You might check the exe/dlls with a tool like Dependency Walker to see if there is a missing component: http://download.cnet.com/Dependency-Walker/3000-2086_4-10052198.html

jasonk