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.
I have two test machines say machine A and B (both 64 bit) .There is a VB6 application which uses the Vbsql OLE Custom control module (Vbsql.ocx).
That VB application runs fine without any errors in machine A but it fails with the below error message when executed in Machine B.
Note: I copied the ocx file from machine A to register it on machine B but it couldn’t be registered the error screenshot is like below.
Both machines doesn’t have VB6 IDE so I could be able to debug.
I found a way to register the VBSQL.OCX file.
Using dependency walker I figured out NTWDBLIB.dll file is missing in machine B so copied into SYSWOW64 folder and registered using the elevated command prompt.