🚀 go-pugleaf

Bill Boland (billbo@ix.netcom.com) wrote:
: >Having a frustrating time trying to call a function in a DLL developed in
: >VC++ 4.0 from Visual Basic 4.0 (32bit). I'm getting VB error 49 (bad DLL
: >calling convention) from the following simple function ...

: I may have a clue since I had a similar situation today.
: If a DLL is compiled with VB 4.0 WITHOUT a module definition file and
: uses  the new __declspec( dllexport ) to declare functions as
: exportable, VB4 cannot seem to understand them. At least that is what
: I discovered today on my own.

Thanks Bill. And thanks Rob Ross of FTP Software, who got back to me after 
phoning MS support about the same problem.
In the root of the VB4 installation directory, there is a file called 
vb4dll.txt that explains a number of issues concerning 32bit DLL's, including
the problems I'd been having.
The solution, as Bill discovered (how many hours do you figure we've all 
collectively wasted ?) is the use of the DEF file.

---
pwhiteside@essa.com
ESSA Software Ltd.