>However, is your FOR expression Rushmore optimizable? It seems to me that in the dark recesses of my (admittedly swiss-cheese) memory, I recall that if it is, and you're updating only one field in a single table, VFP does *not* lock the header.

No, VFP locks the table header regardless. It's just that if the expression is optimized, the header is not locked for nearly as long.


Gavin- Update SQL is probably the best way to go here, but alternatively, you can use

SCAN FOR Whatever
REPLACE
ENDSCAN