There are many possible reasons for this message.
If you have declared a function call into an external DLL, such as a C DLL, or for a Windows API call, then it may fail if the DLL does not exist in the system PATH, or in the same folder as your app.
It will fail if the DLL is correctly found, but the DLL relies upon other files to work. Under those circumstances, the initialisation routine of the DLL will fail, and it will shut down with an error code of 0, telling VB that it failed to load.
Do you know which DLL is the problem?
Are you calling one directly, or is it likely that an OCX in your project is trying to use one?
Thanks for your help. I am new to this and I only had time to investigate this a little further. It is a C dll. I believe VB finds and loads x1.dll and x1.dll tries to load x2.dll. The x2.dll is the one it cant load. I'm still not sure if an OCX is involved, but it does not look like it so far.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.