Bad dll calling convention
4 posts • Page 1 of 1
Bad dll calling convention
Hi,
I receive the following error when I call the Code128Auto procedure: Run-time error '49' Bad Dll calling convention.
I call the dll from visual basic like this:
Text1.Text = Code128Auto(CStr(Text2.Text))
Any suggestions will be helpful.
I receive the following error when I call the Code128Auto procedure: Run-time error '49' Bad Dll calling convention.
I call the dll from visual basic like this:
Text1.Text = Code128Auto(CStr(Text2.Text))
Any suggestions will be helpful.
- dxk240(Legacy Member)
Re: Bad dll calling convention
Are you using Windows DLL?
You may use the Visual Basic code directly. They can be found under \program files\common files\morovia\moroviafonttools. The file name is MoroviaFontTools.vbs.
You may use the Visual Basic code directly. They can be found under \program files\common files\morovia\moroviafonttools. The file name is MoroviaFontTools.vbs.
- glitch (legacy member)
Re: Bad dll calling convention
Update: We found that this is due to the _cdel calling convertion added to the exported functions. We will resolve it in the next version of the Morovia Font Tools upgrade. I will keep you posted.
- glitch (legacy member)
Re: Bad dll calling convention
Thank you for the update. In mean time, I will just use it directly from the source code.
- dxk240(Legacy Member)
4 posts • Page 1 of 1
Return to Microsoft Office (Word, Excel, Access etc) and VB6
Who is online
Users browsing this forum: No registered users and 0 guests