I KNOW i should be searching UT for these tidbits:

I recently have been playing around with the whole
remote view, SPT, Createoffline, NoDataOnLoad, USE AGAIN
performance tradeoffs.

1) Parameterized views are the best for SQL Server views, no doubt.
2) NoDataOnLoad: you have to requery eventually, so no help there
3) Filters on ANYTHING: forget em. (esp if form calls form even with private datasessions, table pointers are moved upon coming back from called form)
4) Local indexes on remote views and SPT cursors: rock if used correctly.

Its these options that im musing about:
Packet size - no difference
fetch size - some difference
fetch memo - if needed have to do it
SQL Prepare - no indicator this ever works on the backend.

I generally do all my brainwork (JOINS) in SQL2000 PROCS/views, then
VFP RV into the SQL2000.

Ive even used Async to watch for the completion of a StoredProc.
(SQL aborts the running SQL if your connection is broken - nice)

So, hmmm, what do you folks think about all these methods for
Forms that people are in all day.
There are advantages to SQL2000 procs/view (mainly incredible speed and security), and advantages to sucking down data into VFP SPT cursors, editing the changes, tableupdating, etc.

I have about 7 combos/lists data-bound to various SPTs or RVs.
Form load time over the 'net sucks.

Thanks,
George