>A couple of questions?
>Are both the VB and VFP in the same package?

Yes, the package includes for components:
1) VFP: Data Access Layer
2) VB: Businsess Rules
3) VB: Creates a VB Collection object, used to store data from VFP
4) VB: Error handler

3 and 4 come from the same DLL. Only 1 and 2 Support transactions. The others do not.

>Can you give more info on what the VFP Dll is doing?
> - opening data?
> - return ??? scattered name objects or custom?
> - does it close it data or leave it open?
> - How does the VB component create/store the VFP object?

The VFP DLL queries tables in a FoxPro DBC using SQL SELECT. It copies the data into VB collection created by a VB component. The VB (business rules) and VFP DLL's pass VB collections to one another. I guess I never did close the tables. They were open shared. So, that should not be problem. Right?

>Also, by calling SetComplete(). The VB object will be 'Deactivated' and the resource it used are gone. Then the next time you call a method on the VB it is reintialized( i think ).

Yes, I am aware of that. When my client test program locks up, it never makes it inside the VFP Init event. It dies on the CreateInstance called from VB. BTW, I have tried CreateObject and New. Both give the same results.

Thanks!