For updating, I use updatable remote views. For read-only data, I use SPT -- SQLExec. When I start my VFP app, I open a dummy remote view that uses a shared connection to Oracle. I use CursorGetProp to get the connection handle used by that view. I can then use that handle in SQLExec. That dummy view is opened in a session class [private DS] that remains open during the life of the app.

SPT is just as viable as a remote view because VFP does exactly the same thing as you would do to submit INSERT, UPDATE and DELETE SQL back to the server. You would only have to do this once if you put your "Table update" code in a custom method of your base form class. You could also use GetNextModified() [with table buffering] and GetFldState() in order to build your SQL string.

Even if you decide to use parameterized remote views, you can still use SPT to perform the updates. Just use the aforementioned GetNextModified and GetFldState functions to loop through the records in the view and to build your SQL string.

>Hello all,
>
>I am looking for some suggestions. I am designing a VFP6 application front end for an Oracle8 database. I am currently accessing the database through Remote Views stored in a DBC that is created on the fly when the User Logs in. The problem that I am having is that it is just too slow.
>
>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.
>
>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.
>
>What are you guys and gals using to connect your Oracle databases? Any help would be greatly appreciated.
>
>Matt