call C++ Dll

Try these;

Declare Sub main0 Lib "test.dll" ((ByVal argc As Long, ByVal inpFileName As String, ByVal
outFileName As String) As Long

call main0 (3, App.Path & "\test.inp", App.Path & "\test.out")

' OR this maybe

Private Declare Function main0 Lib "test.dll" (ByVal argc As Long, ByVal inpFileName As String, ByVal
outFileName As String) As Long


call main0 (3, App.Path & "\test.inp", App.Path & "\test.out")


Cheers
Marcus

Woops extra ( in the first one.

Just open your VB project, go to reference, refer the VC++ dll.

use the normal

Dim objVC as YourDllName

from there, u can straight to use it.

objVC.classmember.

good luck. :>

To xSinbad:

Thank you....but
>Declare Sub main0 Lib "test.dll" ((ByVal argc As Long, ByVal inpFileName As String, ByVal
outFileName As String) As Long
How a Sub returns a Long?

---------------------------------

To ianouii:

Thank you....but
>go to reference, refer the VC++ dll
Are you sure? What you said is for an ActiveX Dll...

Woops.. remove the as long it is not required.

Did you try putting extern "C" in front of your function?

extern "C" int main0(int argc, char *inpFileName, char *outFileName)

Shouldn't the last 2 arguments be passed ByRef?

In C++ you're expecting a pointer to a string.

Private Declare Function main0 Lib "test.dll" (ByVal argc As Long, ByRef inpFileName As String, ByRef
outFileName As String) As Long

Hi Triskelion,

>extern "C" int main0(int argc, char *inpFileName, char *outFileName)

Why we need that?
I used VC++ 6.0 to compile the source into DLL and it works for other simple examples....

That's something to try.

Also try adding
   as integer
to the end of your declare so it is an int instead of a long.

Private Declare Function main0 Lib "test.dll" (ByVal argc As Long, ByVal inpFileName As String, ByVal
outFileName As String) As Integer


DennisL >> Shouldn't the last 2 arguments be passed ByRef?

No... ByVal

>it is an int instead of a long

Well.... should be 'As Long' in VB for 'int' in C++ Dll....

>Shouldn't the last 2 arguments be passed ByRef?
Well...you have never call a C++ Dll with 'As String' :-(

More information:

My code above works if I compile my VB stuff to an exe and then run it. I got the error when I run VB under the design window......

I just made a fresh DLL and called it from Excel.
If you test your DLL with Excel, do you get the same results?

Hi DrDelphi,

In fact, I tried that before you post and I wes going to close the question:-)
What I used is _stdcall and was successfull.
Can you tell me
1. What is the stdcall for
2. What is the difference between _stdcall and STDCALL?

_stdcall is correct. I only capitilized it for emphasis.

the calling convention has to do with how things get cleaned up and the order in which parameters are passed.

Good luck!!

To Triskelion:

Thanks a lot for your comments...I am going to give the points to DrDelphi :-(

To DrDelphi:

If we don't use _stdcall, thins will not cleaned and the parameters will not in order?

Why my original code (without _stdcall) works fine if I compile my VB stuff to an exe and then run it. I got the error only when I run my VB project under the design window......

I can't say for sure, but I suspect that because in the IDE there is an invisible instance of your application running (so that VB can debug it realtime),the DLL has already done what it needed to do once for the "invisible" app, so that it blows up on the "real" app. Of course, I don't know this for sure. I  DO know that the calling convention is the problem, however, having been bitten a time or two myself by the same thing.


Good luck!!
 

Thans a lot for the helps from all experts.