>However, your problem is more severe. You have a hanging reference
>somewhere, most likely related to the FXP loaded into memory or
>possibly some of hte code running inside of it. the hanging ref
>causes the COM object to not unload. You need to fix this or
>you'll cause major problems with resources.

You said it. Out of memory problems where we have to continuously
reboot the IIServer. It's the developement IIServer so no big deal
just not too good in a production environment. :)

>Furthermore, it's not a good idea to use VisualFoxPro.Application
>because it's an EXE server. You should use custom InProc objects.

I guess that is the only way we will have to go.

The whole problem stems from the fact the we can't use VFP ODBC on
remote servers (Microsoft has acknowledged a problem). We've got
to use \\remoteserver\directory type programming directly from VFP
instead of VB with ODBC.

We'll try the DLL next and see how that goes.

Thanks
Gene