>>One thing to try is to open the table Again (in a different session, maybe), replace, update, replace back (maybe just toggle one logical somewhere) and close it in this other alias. That should refresh its disk image, right?
>
>That's an idea. Right after a Tableupdate, maybe just code something like this could send a server update:


I thought of something more brutal - replacing field with itself may not do, so if what you propose doesn't flush it, I'd suggest harder measures:

>=CURSORSETPROP('Buffering',1,'real_one')
>USE real_one AGAIN IN 0 ALIAS temp EXCL
REPLACE numericfield1 with -numericfield1 IN temp
Flush
REPLACE numericfield1 with -numericfield1 IN temp
>USE IN temp
>=CURSORSETPROP('Buffering',5,'real_one')

Or even with buffering of Temp, and forcing a TableUpdate() after each replace...
So, what were the results of testing this (short of extending the mercy of euthanasy to the server)?