In the end, it is the same as re-executing the SQL statement. With SPT, you can do the same thing. Therefore, no limitation exists...

>>>>. If you maintain your rv's in code
>>
>>If you maintain your RV's in code, why not use SPT, and avoid the problems with RV's????? Seems to me that without the VD, any advantage of RV's that may exist, is gone...
>
>There are some limitations to SPT, which is why I still use remote views for updatable data. I have a list of the limitations around here somewhere, but what I can remember off the top of my head is that you can not use VFP's REFRESH() command on SPT, only views. I have found this indespensible. For example, say you have a program that tracks packages. On one form you have a list of many, many packages in a grid. Due to the complex nature of the data and the joins involved, the Requery() for this list of data takes 30 seconds. The form also has a button on it to look at and modify package details. When you click the package details, modify some info and exit the package details any changes you have made needs to be reflected on the package list form. How? If you are using a view you can issue a REFRESH(1,0) and and quickly refresh the data only for the package detail the user was modifying. If you are using SPT you are forced to requery the entire data set again, all 30 seconds of
>it...