>The only way I have been able to deal with this is to not do a Requery in EditMode. VERY confusing.

Not really. What would you have the view do? Throw away the changes? AFAIC, the way that it works is preferable- you should either have to explicitly commit (TABLEUPDATE()) or explicitly revert (TABLEREVERT()) before overwriting a dirty buffer.

Your user interface layer should have the smarts to check for a dirty buffer before doing any action that would overwrite the changes, and possibly ask the user if she wants to save or cancel...