🚀 go-pugleaf

Sylvain Souche wrote:
> 
> Hi,
> 
> I am trying desperatly to call a DLL created with Borland C/C++ 4.5 in a
> VB 3.0 application, but VB always complains about a so called "Bad
> Calling Convention Error". This Error message is not very documented,
> and Borland Help files are worth nothing, so...
> 
> If anyone know about this problem, could you tell me.
> 
> Thanks for e-mail replies
> 
> --
>         Sylvain Souche
>         Sylvain.Souche@supaero.fr

You are probably not exporting the function correctly in the Borland C++ 
DLL.  I am pretty sure that VB 3.0 requires imported functions to be 
'FAR PASCAL'.  

If you are not declaring the function as FAR PASCAL, it will default to 
'CDECL'; which will cause the above mentioned error...

-- Bob T.

Sylvain Souche <souche@supaero.fr> decided to share with us the infinite
reservoirs of wisdom:

>Hi,

>I am trying desperatly to call a DLL created with Borland C/C++ 4.5 in a 
>VB 3.0 application, but VB always complains about a so called "Bad 
>Calling Convention Error". This Error message is not very documented, 
>and Borland Help files are worth nothing, so...

post the dll's code (or at least the part that goes MyFunc(....)) and the
VB declaration you're using.

Jens (balchen@sn.no)
-- 
Newbiehood is not a period of time, it's a way of life.

http://www.sn.no/~balchen
ftp://ftp.sn.no/user/balchen/

Robert Taylor wrote:
> 
> Sylvain Souche wrote:
> >
> > Hi,
> >
> > I am trying desperatly to call a DLL created with Borland C/C++ 4.5 in a
> > VB 3.0 application, but VB always complains about a so called "Bad
> > Calling Convention Error". This Error message is not very documented,
> > and Borland Help files are worth nothing, so...
> >
> > If anyone know about this problem, could you tell me.
> >
> > Thanks for e-mail replies
> >
> > --
> >         Sylvain Souche
> >         Sylvain.Souche@supaero.fr
> 
> You are probably not exporting the function correctly in the Borland C++
> DLL.  I am pretty sure that VB 3.0 requires imported functions to be
> 'FAR PASCAL'.
> 
> If you are not declaring the function as FAR PASCAL, it will default to
> 'CDECL'; which will cause the above mentioned error...
> 
> -- Bob T.

Also, make sure you don't have exception handling enabled for the DLL.

-- jrj

Sylvain Souche <souche@supaero.fr> wrote

>Hi,

>I am trying desperatly to call a DLL created with Borland C/C++ 4.5 in a 
>VB 3.0 application, but VB always complains about a so called "Bad 
>Calling Convention Error". This Error message is not very documented, 
>and Borland Help files are worth nothing, so...

 Hi Sylvain.

Did you use, if necessary,  the "byval" option in your declaration
code?

Michel

tlgnsmd@mail.interpac.be (Michel Lombart) wrote:

>Sylvain Souche <souche@supaero.fr> wrote

>>Hi,

>>I am trying desperatly to call a DLL created with Borland C/C++ 4.5 in a 
>>VB 3.0 application, but VB always complains about a so called "Bad 
>>Calling Convention Error". This Error message is not very documented, 
>>and Borland Help files are worth nothing, so...

> Hi Sylvain.

>Did you use, if necessary,  the "byval" option in your declaration
>code?

>Michel

I have the same problem with VB4.0 and Visual C++ DLLs

The ByVal option is required but this does not always cure the
problem.

VB uses the PASCAL calling convention so the DLL should be compiled
using FAR PASCAL for 16 bit or __stdcall. This still did not cure my
problem but it got me closer.

I have just been infomed that my problem is due to the omission of the
.DEF file by the VC++ compiler now so check that you also have the
DEF file with the .DLL.

Let me know if this helps and if you discover anything that may help
me.

Cheers,

Jolyon.