>The dialogs would not display, the attempt to display them is what would cause the lockup.

I guess that would make sense. Since the dialog is not displaying, how can I tell what the problem is? The error event in the VFP DLL is not firing, nor is the On Error in VB firing either.

My VFP DLL does work when I test it the first time. So maybe there is not enough memory or resource to create an instance of the VFP object.

After reading some of your responses, I have some other questions. First since the VFP DLL accesses FoxPro table rather then SQL or Oracle, the DLL cannot use transactions to rollback the tables. Should I set all the DLL's in my MTS to "Does not use transactions" even though I use SetComplete() and SetAbort()? Does it really make a difference?

My VB DLL Implements ObjectControl. I create some objects in the ObjectControl_Activate() and destroy them in the ObjectControl_Deactivate(). I also create some objects in my VFP DLL's Init. Do I need to release the objects before I do a SetComplete() or SetAbort()? Are there any FoxPro events that fire when SetComplete() or SetAbort() are issued?

In the VB DLL, I do a SetComplete() at the end of every public method. Thus, anytime a public method is called, the Class_Initialize() and ObjectControl_Activate() fire. In VFP, I also do a SetComplete() at the end of every method. The Init event only fires when the VFP component is created. Is there anything comparable to the Class_Initialize() or ObjectControl_Activate() in VB?

Thanks for all the help!