>>If you have optimistic row buffering for the view and move through the view records you don't need TABLEUPDATE because when you move off the record it gets updated automatically
>
>Thanks, I just figured that out 20 seconds ago. I wonder why this occurs in VIEWS and not in other TABLES.
>
>Also, do you have any specs or anecdotel evidence on how much faster VIEW's are than the FILTER command? Edward indicates that he uses VIEWs for everything but I already have FILTERs set up so I am trying to decide if I should rewrite:
> - all my parent/child stuff;
> - just my parent/child grid stuff, or;
> - the parent/child code for the grid the one grid I am having probs with.

Don't have the figures now. I also try to use Views (or SELECT ... into cursor - especially for reports. ) everywhere. There is also another thing - if you use tables and relations and also SQL SELECT - the record pointer in the source tables may move after SQL SELECT and give you unpredictable state of your related tables. If you use just views an SELECTs you don't care where the record pointer is in the source tables.

Nick