>>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.
>
>Good Idea! Unless another user deleted it then! :-) I know GO TOP!

Or store the RECNO() as well and GO to that record if you can't find the PK with a message saying "the former record wsa deleted by another user"...at least, positionally, they'll be near where they were.

>> You could do that, but it screws up GETFLDSTATE(); it'll be difficult to determine user-initiated changes to data and system REPLACEs.
>
>I wonder if using SETFLDSTATE() would be a work around.

I think that there are problems with SETFLDSTATE() as in "it doesn't work"

>I had so much legacy code from VFP 3.0 in my Medical App that I am just now rewriting and modifying all of the forms to support Views. This is my first rewrite for using views. It has been a major learning experience. But I am also modifying it to run on SQL Server with Remote Views.
>
>Thanks for the help. Do you have any apps running using Local Views in this scenario?

Yes I do, and I do pretty much what we have discussed here.