Visual Basic, Has anyone ever seen this before!

Has anyone ever seen this before!

Author	Message
Housene #1 / 2	Has anyone ever seen this before! I have developed code using old VB 4 16 bit version. The development CANNOT be done on a later version of VB! Anyway, I am forced to use DAO 2.5 16 bit to connect to SQL Server 6.5. The problem I am having is, the code executes perfectly in an uncompiled state. However, if I compile the code, the program does not recognize the DSN that I have previously used successfully while running the program from VB. Eventually, the program gives me an error "Application Error" - "Invalid Dynalink". Has anyone ever heard of such a thing? Is there any explanation for this or resolution to it. Is there an API or funciton that can retreive or validate dynalinks that exist on a machine? Please don't say upgrade because that's not an option. Thank You, for any assistance you can provide.
Sun, 16 Dec 2001 03:00:00 GMT

William P. Cla #2 / 2	Has anyone ever seen this before! Quote: > I have developed code using old VB 4 16 bit version. > The development CANNOT be done on a later version of VB! > Anyway, I am forced to use DAO 2.5 16 bit to connect to SQL Server 6.5. > The problem I am having is, the code executes perfectly in an uncompiled > state. > However, if I compile the code, the program does not recognize the DSN > that I have > previously used successfully while running the program from VB. > Eventually, > the program gives me an error "Application Error" - "Invalid Dynalink". > Has anyone ever heard of such a thing? Is there any explanation for > this or resolution to it. > Is there an API or funciton that can retreive or validate dynalinks that > exist on a machine? > Please don't say upgrade because that's not an option. > Thank You, for any assistance you can provide. House, Invalid Dynalink usually means that the app is trying to use an old version of a DLL that is missing an entry point it is looking for. If your compiled app is in a different directory than the IDE, then it is possible that it is trying to load a different version of some DLL than it loads when run from the IDE. Unfortunately, it sounds like you are running under Win3.1, which doesn't bother to tell you which DLL is the problem. When your app tries to load a DLL it will first look in its own directory, then in Windows and Windows\System (if I recall correctly). So, the problem could be that you have an older version of some DLL in your app's directory and a newer version in Windows\System (which is the one the IDE is using), OR you have a newer version in the VB directories (which the IDE uses) and an older version in Windows\System (which the app is using). Can't say for sure this is the problem, but it is worth checking. -- Bill Clay
Mon, 17 Dec 2001 03:00:00 GMT

Page 1 of 1

[ 2 post ]