I’m creating a VFP6 app which needs to access a SQL7 backend. I setup parameterized views to the data for all files which the user may need to update. Many forms need to use multiple views. Most of the time, the view is first opened with the NODATA clause. If I set “Share Connection” on, I get a “Function Sequence Error” from ODBC. Also, if I set FetchSize to –1 to eliminate the “Connection is Busy” error, my performance drops substantially. One form load can take up to 5 minutes with Fetchsize set to -1. I had to set “Share Connection” off just to load the form. I’m concerned about using up 5 SQL connections to load a form.

How can views effectively be used on a client/server environment, if sharing a connection is so slow? Is there a better way? I’m sharing 1 connection for all my SPT statements and do not seem to have any speed problems. Should I be using SPT for everything and forget about getting views to work efficiently? Please help.

Thanks.
Monique