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?
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
