>2) I would like to use the VFP back end as a calculator for the front end with tables remaining open in the back end from one call to the next. The .NET app would make a call to stored procedure via OleDb. The stored procedure then opens an app (if not already open) and passes the requested command as well as id of calling session. VFP app then figures out which datasession to select, performs call and returns result, leaving tables open ready for next call.
>

The OleDB driver has limitations. For example, I don't think CreateObject() is supported. A COM object may be a better choice for this.

Also, the DDEX driver coming with Sedna will make it easier to deal with VFP data in Visual Studio.