For Any Use & On Any Platform
Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
c dll calling from VB6 - Parameter Error
Posted on 2013-01-06
Private Declare Function SSR_GetGeneralLogData Lib "c:\Windows\System32\zkemk
ByVal dwEnrollNumber As String, ByVal dwSize As Long, ByVal dwVerifyMode As Long, _
ByVal dwInOutMode As Long, ByRef dwYear As Long, ByRef dwYear As Long, ByRef dwMonth As Long, ByRef dwDay As Long, ByRef dwHour As Long, ByRef dwMinute As Long, ByRef dwsecond As Long, ByRef dwWorkCode As Long) As Boolean
Dim ver As String
Dim vMachineNumber
Dim dwEnrollNumber As String
Dim dwVerifyMode As Long
Dim dwInOutMode As Long
Dim timeStr As String
Dim i As Long
Dim dwMachineNum As Long
Dim dwEMachineNum As Long
Dim dwYear As Long
Dim dwMonth As Long
Dim dwDay As Long
Dim dwHour As Long
Dim dwMinute As Long
Dim dwsecond As Long
Dim dwWorkCode As Long
Dim dwReserved As Long
Dim s As String
'DLL PARAMETERS
'[in] LONG dwMachineNumber,
'[out] BSTR* dwEnrollNumber,
'[out] LONG* dwVerifyMode,
'[out] LONG* dwInOutMode,
'[out] LONG* dwYear,
'[out]LONG* dwMonth,
'[out] LONG* dwDay,
'[out] LONG* dwHour,
'[out] LONG* dwMinute,
'[out] LONG* dwSecond,
'[out,retval] VARIANT_BOOL* pVal
If CZKEM1.ReadGeneralLogData(
BUFFER OVERRUN AFTER EXECUTING FOLLOWING LINE
While CZKEM1.SSR_GetGeneralLogDa
DoEvents
i = i + 1
'Write to database
'MsgBox strSQL
''''''' dbs.Execute strSQL, dbFailOnError
Wend
End If
MsgBox "Processed Successfully!"
End If
ByVal dwEnrollNumber As String, ByVal dwSize As Long, ByVal dwVerifyMode As Long, _
ByVal dwInOutMode As Long, ByRef dwYear As Long, ByRef dwYear As Long, ByRef dwMonth As Long, ByRef dwDay As Long, ByRef dwHour As Long, ByRef dwMinute As Long, ByRef dwsecond As Long, ByRef dwWorkCode As Long) As Boolean
Dim ver As String
Dim vMachineNumber
Dim dwEnrollNumber As String
Dim dwVerifyMode As Long
Dim dwInOutMode As Long
Dim timeStr As String
Dim i As Long
Dim dwMachineNum As Long
Dim dwEMachineNum As Long
Dim dwYear As Long
Dim dwMonth As Long
Dim dwDay As Long
Dim dwHour As Long
Dim dwMinute As Long
Dim dwsecond As Long
Dim dwWorkCode As Long
Dim dwReserved As Long
Dim s As String
'DLL PARAMETERS
'[in] LONG dwMachineNumber,
'[out] BSTR* dwEnrollNumber,
'[out] LONG* dwVerifyMode,
'[out] LONG* dwInOutMode,
'[out] LONG* dwYear,
'[out]LONG* dwMonth,
'[out] LONG* dwDay,
'[out] LONG* dwHour,
'[out] LONG* dwMinute,
'[out] LONG* dwSecond,
'[out,retval] VARIANT_BOOL* pVal
If CZKEM1.ReadGeneralLogData(
BUFFER OVERRUN AFTER EXECUTING FOLLOWING LINE
While CZKEM1.SSR_GetGeneralLogDa
DoEvents
i = i + 1
'Write to database
'MsgBox strSQL
''''''' dbs.Execute strSQL, dbFailOnError
Wend
End If
MsgBox "Processed Successfully!"
End If
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
5-
2
- +3
12 Comments
Active today
Try declaring dwEnrollNumber as a fixed-length string, large enough to accommodate the expected text, e.g.
Dim dwEnrollNumber As String * 100
Dim dwEnrollNumber As String * 100
Thnx...
But I have tried that even....
& I have an application installed, which works fine with this dll
But I have tried that even....
& I have an application installed, which works fine with this dll
From this link:
http://msdn.microsoft.com/en-us/library/aa263531%28v=vs.60%29.aspx
Some DLLs may be written specifically to work with Automation data types like BSTR, using procedures supplied by Automation.
Because Visual Basic uses Automation data types as its own data types, Visual Basic arguments can be passed by reference to any DLL that expects Automation data types. Thus, if a DLL procedure expects a Visual Basic string as an argument, you do not need to declare the argument with the ByVal keyword, unless the procedure specifically needs the string passed by value.
Some DLL procedures may return strings to the calling procedure. A DLL function cannot return strings unless it is written specifically for use with Automation data types. If it is, the DLL probably supplies a type library that describes the procedures. Consult the documentation for that DLL.
A DLL procedure can modify data in a string variable that it receives as an argument. However, if the changed data is longer than the original string, the procedure writes beyond the end of the string, probably corrupting other data.
You can avoid this problem by making the string argument long enough so that the DLL procedure can never write past the end of it
Then try
Dim dwEnrollNumber As String * 255
http://msdn.microsoft.com/en-us/library/aa263531%28v=vs.60%29.aspx
Some DLLs may be written specifically to work with Automation data types like BSTR, using procedures supplied by Automation.
Because Visual Basic uses Automation data types as its own data types, Visual Basic arguments can be passed by reference to any DLL that expects Automation data types. Thus, if a DLL procedure expects a Visual Basic string as an argument, you do not need to declare the argument with the ByVal keyword, unless the procedure specifically needs the string passed by value.
Some DLL procedures may return strings to the calling procedure. A DLL function cannot return strings unless it is written specifically for use with Automation data types. If it is, the DLL probably supplies a type library that describes the procedures. Consult the documentation for that DLL.
A DLL procedure can modify data in a string variable that it receives as an argument. However, if the changed data is longer than the original string, the procedure writes beyond the end of the string, probably corrupting other data.
You can avoid this problem by making the string argument long enough so that the DLL procedure can never write past the end of it
Then try
Dim dwEnrollNumber As String * 255
I've never had to do exactly what you are trying, but my experience says that your best bet might be to:
1. Change your declaration for the parameter to 'ByRef'
2. Rather than passing 'dwEnrollNumber', try passing 'VarPtr( dwEnrollNumber )'
Private Declare Function SSR_GetGeneralLogData Lib "c:\Windows\System32\zkemk
ByRef dwEnrollNumber As String, ByVal dwSize As Long, ByVal dwVerifyMode As Long, _
ByVal dwInOutMode As Long, ByRef dwYear As Long, ByRef dwYear As Long, ByRef dwMonth As Long, ByRef dwDay As Long, ByRef dwHour As Long, ByRef dwMinute As Long, ByRef dwsecond As Long, ByRef dwWorkCode As Long) As Boolean
While CZKEM1.SSR_GetGeneralLogDa
1. Change your declaration for the parameter to 'ByRef'
2. Rather than passing 'dwEnrollNumber', try passing 'VarPtr( dwEnrollNumber )'
Private Declare Function SSR_GetGeneralLogData Lib "c:\Windows\System32\zkemk
ByRef dwEnrollNumber As String, ByVal dwSize As Long, ByVal dwVerifyMode As Long, _
ByVal dwInOutMode As Long, ByRef dwYear As Long, ByRef dwYear As Long, ByRef dwMonth As Long, ByRef dwDay As Long, ByRef dwHour As Long, ByRef dwMinute As Long, ByRef dwsecond As Long, ByRef dwWorkCode As Long) As Boolean
While CZKEM1.SSR_GetGeneralLogDa
A few follow up details:
When you pass a VB String to a dll ByVal, you don't really pass it "By Value". What actually happens is that the VB Unicode String is converted to ANSI and a char* of the ANSI string is sent to the dll. When the function returns, the ANSI string at the char* is converted into a VB Unicode String and the original VB String is updated with the new value. So in reality, passing a VB String ByVal still passes ByRef. And BTW, if the dll makes the char* longer, bad things can happen when VB goes to return the results back into the original string.
When you pass a VB String to a dll ByRef, I believe that a BSTR is sent to the dll. I don't know that I've ever passed a VB String ByRef, but I do know that if you declare a dll function as returning a BSTR (and not a BSTR*) that you can have code that looks like this:
Declare Function DllThatReturnsBSTR() as String
Dim Str
Str = DllThatReturnsBSTR();
And finally, it's widely known today, but there is a 'hidden' function in VB, VarPtr(). It returns a pointer to the variable.
When you pass a VB String to a dll ByVal, you don't really pass it "By Value". What actually happens is that the VB Unicode String is converted to ANSI and a char* of the ANSI string is sent to the dll. When the function returns, the ANSI string at the char* is converted into a VB Unicode String and the original VB String is updated with the new value. So in reality, passing a VB String ByVal still passes ByRef. And BTW, if the dll makes the char* longer, bad things can happen when VB goes to return the results back into the original string.
When you pass a VB String to a dll ByRef, I believe that a BSTR is sent to the dll. I don't know that I've ever passed a VB String ByRef, but I do know that if you declare a dll function as returning a BSTR (and not a BSTR*) that you can have code that looks like this:
Declare Function DllThatReturnsBSTR() as String
Dim Str
Str = DllThatReturnsBSTR();
And finally, it's widely known today, but there is a 'hidden' function in VB, VarPtr(). It returns a pointer to the variable.
Oh, and now that I remembered the VarPtr function, you might also try replacing the VarPtr I listed above with either StrPtr or ObjPtr. Don't know if they will work, but StrPtr is defined as "gives the memory address of the contents of a string". That might just be the BSTR* (but I'm not sure). But it is worth a try.
http://www.codeproject.com/Articles/5685/Pointers-in-Visual-Basic-using-Undocumented-Functi
http://www.codeproject.com/Articles/5685/Pointers-in-Visual-Basic-using-Undocumented-Functi
One last idea. Try changing the declare to 'ByRef' and 'As Any').
Private Declare Function SSR_GetGeneralLogData Lib "c:\Windows\System32\zkemk
ByRef dwEnrollNumber As Any, ByVal dwSize As Long, ByVal dwVerifyMode As Long, _
ByVal dwInOutMode As Long, ByRef dwYear As Long, ByRef dwYear As Long, ByRef dwMonth As Long, ByRef dwDay As Long, ByRef dwHour As Long, ByRef dwMinute As Long, ByRef dwsecond As Long, ByRef dwWorkCode As Long) As Boolean
The try passing the original variable: dwEnrollNumber
and try passing the pointer to the original value: VarPtr( dwEnrollNumber )
and try passing the pointer to the contents: StrPtr( dwEnrollNumber )
and finally the pointer to the object: ObjPtr( dwEnrollNumber ).
Again, I've never had to try exactly what you are doing (and currently don't have any test code or the time to look for the exact solution). But one of those combinations should eventually work.
Just to rehash:
1. Try declaring the variable ByRef and ByVal
2. Try declaring the variable 'As String' and 'As Any'
3. Try passing the variable, VarPtr(variable), StrPtr(variable), and ObjPtr(variable).
Try all the possible combinations of these options. If it still does not work, then the last thing I can think of:
Declare the variable ByVal and As Long (good for passing pointer) and pass VarPtr, StrPtr, and ObjPtr.
Otherwise, the only other thing I can even contemplate on how to fix the issue involved changing the dll (to take something OTHER than a BSTR*... such as a BSTR or char* instead).
3. Also try 'ByRef dwEnrollNumber As Long' (good for passing pointers).
4.
and finally try passing the
Private Declare Function SSR_GetGeneralLogData Lib "c:\Windows\System32\zkemk
ByRef dwEnrollNumber As Any, ByVal dwSize As Long, ByVal dwVerifyMode As Long, _
ByVal dwInOutMode As Long, ByRef dwYear As Long, ByRef dwYear As Long, ByRef dwMonth As Long, ByRef dwDay As Long, ByRef dwHour As Long, ByRef dwMinute As Long, ByRef dwsecond As Long, ByRef dwWorkCode As Long) As Boolean
The try passing the original variable: dwEnrollNumber
and try passing the pointer to the original value: VarPtr( dwEnrollNumber )
and try passing the pointer to the contents: StrPtr( dwEnrollNumber )
and finally the pointer to the object: ObjPtr( dwEnrollNumber ).
Again, I've never had to try exactly what you are doing (and currently don't have any test code or the time to look for the exact solution). But one of those combinations should eventually work.
Just to rehash:
1. Try declaring the variable ByRef and ByVal
2. Try declaring the variable 'As String' and 'As Any'
3. Try passing the variable, VarPtr(variable), StrPtr(variable), and ObjPtr(variable).
Try all the possible combinations of these options. If it still does not work, then the last thing I can think of:
Declare the variable ByVal and As Long (good for passing pointer) and pass VarPtr, StrPtr, and ObjPtr.
Otherwise, the only other thing I can even contemplate on how to fix the issue involved changing the dll (to take something OTHER than a BSTR*... such as a BSTR or char* instead).
3. Also try 'ByRef dwEnrollNumber As Long' (good for passing pointers).
4.
and finally try passing the
I got an opportunity to try a test. It looks like the 1st suggestion of my previous post appears to work (simply declare the variable 'ByRef' and 'as Any').
Here's my test code:
C Source Code for ChkMan32.dll
==========================
long __declspec(dllexport) FAR PASCAL TestBSTR(char* psz, BSTR* strOut )
{
int len = strlen( psz );
*strOut = SysAllocStringByteLen( psz, len );
return 0;
}
VB BAS file Declaration
===================
Public Declare Function TestBSTR Lib "ChkMan32" Alias "_TestBSTR@8" (ByVal psz As String, ByRef strOut As Any) As Long
VB Code
=======
Dim str As String
Dim psz As String
psz = "ABCDEFG"
Call TestBSTR(psz, str)
MsgBox str
"ABCDEFG" appeared in the Message Box
Here's my test code:
C Source Code for ChkMan32.dll
==========================
long __declspec(dllexport) FAR PASCAL TestBSTR(char* psz, BSTR* strOut )
{
int len = strlen( psz );
*strOut = SysAllocStringByteLen( psz, len );
return 0;
}
VB BAS file Declaration
===================
Public Declare Function TestBSTR Lib "ChkMan32" Alias "_TestBSTR@8" (ByVal psz As String, ByRef strOut As Any) As Long
VB Code
=======
Dim str As String
Dim psz As String
psz = "ABCDEFG"
Call TestBSTR(psz, str)
MsgBox str
"ABCDEFG" appeared in the Message Box
Featured Post
This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Background
What I'm presenting in this article is the result of 2 conditions in my work area:
We have a SQL Server production environment but no development or test environment; andWe have an MS Access front end using tables in SQL Server but we a…
It was really hard time for me to get the understanding of Delegates in C#. I went through many websites and articles but I found them very clumsy. After going through those sites, I noted down the points in a easy way so here I am sharing that unde…
The goal of this video is to provide viewers with basic examples to understand and use while-loops in the C programming language.
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code.
This l…
- Microsoft Office
- Office 365
- Microsoft Access
- VBA
- Microsoft Excel
- Visual Basic Classic
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month7 days, 6 hours left to enroll
Earn Certification
CompTIA IT Fundamentals
$49.00$44.10
622 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.