Ok... I have a DLL written in VC++ that exports a function that uses the __cdecl calling convention and I want to call the function from a VB program. However VB uses the __stdcall calling convention so I can't use the DLL (actually I haven't tested that, but I'm sure I won't be albe to use the DLL).

So the question is: Is there anything I can do to force VB use the __cdecl calling convention? What can I do? Ideas?

I'd prefer not to modify the DLL code, because the DLL will be used by another program too, and it needs to stay as __cdecl. I've thought about making another DLL (in VC++) that exports a __stdcall function that calls the __cdecl one in the original DLL, however I'm not very good in VC++ and don't know how to call an exported function of a DLL .

Thanks for your help!

I believe all the functions in the Win32 API use __cdecl, but VB can still use them.

Typical VB API access declaration:
Private Declare Function RegOpenKeyEx Lib "advapi32.dll" Alias "RegOpenKeyExA" (ByVal hKey As Long, ByVal lpSubKey As String, ByVal ulOptions As Long, ByVal samDesired As Long, phkResult As Long) As Long

'Template':
Private Declare Function <functionname> Lib "<filename>.dll" Alias "<funcnamefromdll>" (<arglist>) As <returntype>

EDIT: Tell you what, you post the function header from your DLL, and I'll see if I can come up with a VB declaration statement to allow you to use it.

quote:

---

Originally posted by raceprouk
I believe all the functions in the Win32 API use __cdecl, but VB can still use them

---

quote:

---

Originally posted by raceprouk
Typical VB API access declaration:
Private Declare Function RegOpenKeyEx Lib "advapi32.dll" Alias "RegOpenKeyExA" (ByVal hKey As Long, ByVal lpSubKey As String, ByVal ulOptions As Long, ByVal samDesired As Long, phkResult As Long) As Long

'Template':
Private Declare Function <functionname> Lib "<filename>.dll" Alias "<funcnamefromdll>" (<arglist>) As <returntype>

---

quote:

---

Originally posted by raceprouk
EDIT: Tell you what, you post the function header from your DLL, and I'll see if I can come up with a VB declaration statement to allow you to use it.

---

code:

---

int __cdecl TRADUCIR(const char *p_fichero_iso,const char *p_fichero_mac,const char *p_fichero_mec)

---

code:

---

Public Declare Function TRADUCIR Lib "traductor.dll" (ByVal iso As Long, ByVal mac As Long, ByVal mec As Long) As Long

---

code:

---

int __stdcall TRADUCIR__stdcall(const char *p_fichero_iso,const char *p_fichero_mac,const char *p_fichero_mec) {
    return TRADUCIR(p_fichero_iso,p_fichero_mac,p_fichero_mec);
}

---

code:

---

Public Declare Function TRADUCIR Lib "traductor.dll" Alias "TRADUCIR__stdcall" (ByVal iso As Long, ByVal mac As Long, ByVal mec As Long) As Long

---

I've really got to start reading up on stuff before answering questions...

Well Choli, it seems that you haven't searched whole MSDN and Microsoft KB... (OK, I'm joking )

Would this work?

code:

---

Public Declare Function TRADUCIR CDecl Lib "traductor.dll" (ByVal iso As Long, ByVal mac As Long, ByVal mec As Long) As Long

---

quote:

---

Originally posted by Mnjul
Well Choli, it seems that you haven't searched whole MSDN and Microsoft KB...

---

quote:

---

Originally posted by Mnjul
Would this work?

---

Choli,

VB6 hasta donde se, solo puede usar una DLL que usen la convension STDCALL.
La unica forma que encuentro es que cambies la funcion de CDECL a STDCALL para que pueda ser usada por un programa de VB6.
Cuando lo quieras llamar a la DLL desde otro programa tienes que asigname STDCALL tambien porque si no leera pura basura la DLL.
te escribo en castellano porque mi ingles es malo
chao

And in English?