>>>. 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...

No, the VD is not the advantage to views. The advantage to views it...

1. Useing a view creates a read-write buffered cursor.

2. When a tableupdate() is issued C++ speed code builds the required updates and passed them to the back end.

3. Remote view updates are automatically wrapped in a transaction.

4. You write much less code due to item 1 & 2.

5. This is one of the best ways to create a C/S and Local Table version of your product with very little code differences.

Although I have since learned that hard coding ANY SQL, RV, SPT or SP is the WRONG WRONG WRONG way to do it, and am working on a VFP Persistence framework which will eliminate the need to write SQL code.

BOb