Thanks John,
the save of the view is done with TableUpdate(1,.T.) command
The first tab has the grid with the table listed, click on a row and then all other tabs show that information. On the deactivate of this row I have the tablerevert and requery commands. If I go into tab2 then whatever I have changed in the background dbf will be shown on the view so I'm happy there. However if I go straight to tab 5 which has a child view I get the confirmation that the view has changed, wait windows, but it doesn't actually change.
~M

>Mark,
>
>Sounds as if the Views are updating all fields rather than just changed fields, causing the last save to overwrite earlier changes. Usually a VFP view would not update data that has not changed, allowing users of VFP apps safely to change different parts of the same record as you describe. I have seen stale data overwriting newer data if controls are bound to objects or memvars SCATTERed and then GATHERed into the table or view, since effectively that does update every field. Can you tell us how the save is done?