🚀 go-pugleaf

billbo@ix.netcom.com (Bill Boland) wrote:

>a09748@giant.mindlink.bc.ca (ESSA) 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 ...
>>
<snip> non-working code

>Bill Boland
>--------
>billbo@ix.netcom.com
>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.

Yes a module definition file seems to be necessary, VB couldn't find
the C function names until I included one.

However, this doesn't quite explain the "Bad Calling Convention"
error.

Check out VB4DLL.TXT in the \VB directory on the CDROM. It should help
explain all.

Cheers,
	lauren :}