Hi Chris,

Thanks for your reply. If you look at the code, I am calling the REQUERY() to pull the data from the network to update my local view. The view looks perfect (GetFldState reporting all fields not modified) when it loops back around after the TableRevert-Requery. When I increment the ID number, that is the only field registering as "changed". In every case, the TableUpdate still failes.

For some reason, it appears that the the original copy of the base table is being used for comparison when checking for changes - the Requery() that properly refreshed the view does not affect the copy of the base table open in the same environment. I checked the base table and its' buffermode is at 0 (none).

If I stop the process in the debugger and browse the table it shows the updated value - if I don't browse the table, it shows the original. In addition, if I close the copy of the base table after the view opens it (automatically), everything works as expected - a new copy of the underlying table is opened when the TableUpdate() is called. Very messy workaround.

I'm searching for a technique that I can use in ALL situations (one code base/methodology) that will work using native VFP tables or SQL (any flavor). And it showed such promise....

Thanks again!