Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

"Need superior Guru help with C DLL for VB"

"Need superior Guru help with C DLL for VB"

I need a guru to help me!

I have a C DLL that is being developed, however in VB I get the following
error with the following C interfaces to the DLL: (My VB Code is at the
bottom of this message)

What can be done so these errors don't occur in the VB IDE (or compiled as
pseudocode)?

I am using VB 5 and have no problems declaring or utilizing DLL's in general.



With the following code I get the following error when attempting to run the
corresponding VB code in the VB IDE (or compiled as p-code): "Run-Time error
49: Bad DLL Calling convention". NOTE: If I compile the VB Code down below to
n native code exe it appears to work correctly. (However, because this is not
good enough for me, since it won't work in the IDE, then something may be
declared incorrectly and memory errors might occur later on)

SOX1 (withOUT stdcall):
_declspec(dllexport) void __stdcall SOX(LPCSTR, LPCSTR, LPCSTR, LPCSTR,
LPCSTR);
LPCSTR            cmd,
LPCSTR            stdout_fl,
LPCSTR            out,
LPCSTR            stderr_fl,
LPCSTR            err)
void            SOX(
{...}

The following code produces the following error when executed in the VB IDE
(when run as p-code) or as a native code executable: "Run-Time Error 453:
Can't find entry point in sox2.dll"

SOX2 (WITH stdcall):
_declspec(dllexport) void SOX(LPCSTR, LPCSTR, LPCSTR, LPCSTR, LPCSTR);
void __stdcall      SOX(
LPCSTR            cmd,
LPCSTR            stdout_fl,
LPCSTR            out,
LPCSTR            stderr_fl,
LPCSTR            err)
{...}


Here is my VB Declaration:

'Test DLL1
Private Declare Sub SOX Lib "sox1.dll" (ByVal Cmd As String, ByVal
OutMessFile As String, ByVal OutMess As String,

'Test DLL2
'Private Declare Sub SOX Lib "sox2.dll" (ByVal Cmd As String, ByVal
OutMessFile As String, ByVal OutMess As String,
ByVal ErrMessFile As String, ByVal ErrMess As String)

Here is the VB Function that calls the DLL:
Function TestCode()
Dim a As String
Dim b As String
Dim c As String
Dim d As String
Dim e As String

a = txtIn.Text
b = "out.tmp"
c = String(513, " ")  'Create a buffer of 513
d = "err.tmp"
e = String(513, " ")  'Create a buffer of 513
 
SOX a, b, c, d, e

txtOut.Text = c
txtErr.Text = e
End Function
0
bre342
Asked:
bre342
1 Solution
 
muffinthedogCommented:
Sure it taint BSTR your passing then
LPSTR myString;
myString = (LPSTR)passedBSTR;

and are you using a DEF file?

0
 
JimKarabatsosCommented:
Umm, you do need to use stdcall, so we'll work with the sox2 dll.  The problem is that the C compiler is exporting the name in lower case.  I think you will find that you need to do one of two things:

1. tell the linker that you want to presrve case for exported symbols, or

2. use this declaration:

Private Declare Sub SOX Lib "sox2.dll" Alias "sox" _
  (ByVal Cmd As String, ByVal OutMessFile As String, _
   ByVal OutMess As String, ByVal ErrMessFile As String, _
   ByVal ErrMess As String)

-- Jim
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now