Hi all,
I am trying to access Btrieve 6.15 Database through the Btrieve
API from wbtrv32.dll(btrieve 6.15 version). Indeed, I have succesfully
get everything done. However, whenever I am under vb6 debug mode, I
get error 49 "Bad dll Calling convention". This does not happen when I
compile the exe and run the executable. So, I am just wondering if
anybody faced this kind of issue before and may be you can share with
me.

Some additional information and specific questions:
(i) Is wbtrv32.dll(Btrieve 6.15) using _stdcall?
Since dll not using _stdcall may result bad dll calling
convention and
miss up the stack.

(ii) My function declarations:
Declare Function BTRCALL Lib "wbtrv32.dll" (ByVal OP%, _
ByVal Pb As Any, _
BtRec As Any, _
DataLen As Integer, _
KeyBuf As Any, _
ByVal KeyLen%, _
ByVal KeyNo%) As Integer

(iii) I don't know if the following information is equivalent.
I tested all my code with wbtrv32.dll(Pervasive 2000i) and
there is no problem during runtime and debug mode.

(iv) The Bad Dll Calling Convention does not occur on the line
BTRCALL is called:

Suppose:
Sub A()
... some code
A= BtRcall(...)
... some code
End sub

The Bad Dll calling convention occurs on my own function A.

Thanks very much for your kind attention and hope that U can help!

I would download the Pervasive.SQL V8 SDK and try using that with VB6
(use the wbtrv7.dll interface instead of wbtrv32.dll) since it is
supported and once you get everything going, update your production
systems to V8. You may get an old Btrieve6/VB6 programmer to help you
out, but that is no longer supported by Pervasive,however the Btrieve
interfaces are supported with Pervasive.SQL V8 and you can get support
directly from Pervasive's excellent Developer Support team or you can
get help on the Pervasive forum DevTalk off the Pervasive site -
www.pervasive.com/devtalk.

Good luck,
JR