Hi George...

Very insightful...

This may be the #1 trap that folks fall into when going to SQL; employing a local data mind-set to remote data. Take a table with 100K records. In VFP, it is there, instantly. If you are using local views, there is no difference. When you upsize, you have now hit the wall. Unfortunately, applications are often coded under the assumption that the data is already there. For example, a line of code might do a SEEK. This necessarily assumes the data is available on the client. When dealing with remote data, one should never make this assumption

I don't know if I have interpreted your interpretation correctly. I hope I have. If I have not, then please steer me in the right direction.

And, as a personal note, thanks for adding to the discussion; that is what I have been trying to instill. You are one of the truly talented people I see up here and your comments are most welcome and appreciated...



>JVP,
>
>PMFJI, but I've been following this and other related threads on the subject of RVs and SPT/SP. I wonder if you'd care to comment on the feelings I'm getting on the subject. Please, however, note that I'm in the midst of "getting my feet wet" with SQL Server, so my reaction may be incorrect. If so, any comments would be appreciated.
>
>I'm getting the feeling that many folks would are using RVs tend to approach them the same way they would native tables, which are ISAM type. If so, and there are related tables involved, this might explain complaints of slowness in retrievals and updates, since multiple trips across the wire are required.