I'd try taking OUT you 'set record locks' part and see if that helps.
Table buffering is supposed to perform its own locking BUT if I read the docs correctly, *if* you do your own then YOU are responsible for unlocking them INDIVIDUALLY.

good luck


>From time to time I see references to similar problems regarding data not being written to disk or VFP working on stale information. I do the following:
>
>Set record locks
>Set the buffering for several tables to optimisitic table buffering.
>Make changes to the tables.
>BEGIN TRANSACTION
>TABLEUPDATE
>END TRANSACTION or ROLLBACK
>UNLOCK IN for all tables
>Turn off buffering
>
>VFP cannot find the changed data. However if I add a FLUSH immediately after turning off buffering, VFP finds the changed data. I am using VFP 8.0 on Windows XP Pro workstation, no network involved, and yes write caching is turned off.
>
>Is using FLUSH to make sure VFP gets the latest data reliable, or is there something sort of a window during which one cannot be sure which version of data is available? Some of these changes are fairly large, so checking each updated item against OldValue would be extremely tedious.
>
>Thanks in advance,
>David