>If I issue a REQUERY() do you think I should attempt to keep the current record displayed?
Oh, absolutely. Before you requery, store the primary key to a var or property and then LOCATE to get back to the same record. This will work unless you have a huge view in which case the locate may take a while.
>Do you think it is also possible to just fetch the current record into another view or use CURVAL() to replace the current record in the Local View and then do the edit?
You could do that, but it screws up GETFLDSTATE(); it'll be difficult to determine user-initiated changes to data and system REPLACEs.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05