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?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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?
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.