>>There are very few dll files that can't be used in
>>Visual Foxpro that can be used in Visual Basic.
>>I have had this error before,but I can't remember what I did
>>do get rid of it. The only thing is I can think of is to change
>>INTEGER lpfnMsgCallback to String @lpfnMsgCallback and pass it
>>as 0. I am pretty sure that VFP can't handle Call Back functions.
>>I would then look at VB examples to see what types they are sending it.
>
>I will try your suggestions tomorrow. BTW, do you know how one can tell if a DLL will work in VFP?

Sure! You try and see if it works or not! :)