>>I have experimented with using SQL Passthrough however by doing so I must >>write all of the INSERT,UPDATE, and DELETE statements in SQL rather than the >>native fox. Plus I cannot use parameterized views to return just the records >>that I need. I have to code each of these in SQL Passthrough.

Once you pull a View locally in FoxPro you can use CursorSetProp() to set the tables and fields you wan tto update. Then do your changes in FoxPro and issue a tableupdate(). SQL Passthrough can be parameterized like any predefined view.

>>
>>The third thing that I have noticed is that the Oracle connection is only open when the views are in use. With SQL Passthrough the connection remains open until a sqldisconnect is executed.
>>

>I don't see this as a problem. When you are done with a connection, close it.

The problem with closing connection when the remote view is closed is that it takes time to re-open a connection for the next remote view. If you keep the connection open, then subsequent remote views will open very quickly.

Our approach has been to open a remote view at the start of the app and leave it open. This has reduced form instantiation times from several seconds to a fraction of a second. If you use dbgetprop() to get the connection handle for the initial remote view, you can also use it for your SQL pass through commands. This lets you wrap SQLUPDATES and updates to remote views together in single transaction.

A possible problem with this approach is if there are too many users, too many connections may be open at one time. My impression is that this needs to be in the thousands before it's a problem.