I have a VFP 5.0 app running at a client site on a Novell 4.11 network that performs a transaction updating about 7 files after using table buffering to make the necessary changes. This app has been running with no problem, until recently when I made a change to the way primary keys were assigned to new records. The primary key routine is called each time a record is inserted into any table. It uses its own table to determine new keys, and is updated immediately with the results (no buffering or transaction). The only change I made to this routine was to lock the key table record and the header record of the table into which I'm inserting the value for the entire duration of the assignment process. Both locks are then released. The later transaction process bombs when updating the first table in the transaction, which definitely does not get any new records during the process. FoxPro Acts like it is a record lock problem. Anyone have any ideas?

Thanks in advance for your help!
-Deri Gawthrop