Hi all,

I have an application that normally has approximately 100-150 concurrent users logged in per day. Each user generates about 70 records per day. The main form used is a basic data entry screen, which only ever inserts data into a series of tables. The main portion of the update code does an INSERT INTO from a series variables into the row buffered table fields, then a TABLEUPDATE() to write the data through to the database.

Approximately 10%-15% of the time, the application will generate 'Record is in use' error during the update process for any given user. Now, since I am not locking any records manually...ever...I am confused. An INSERT INTO should handle the locking internally, right?

Has anyone else ever seen this behaviour? I've used the same setup in other applications without these errors, however the record insertion traffic has never been this high. The application is written in VFP 5.0 and runs on NT 4.0.

Any help or suggestions as to the root of the problem would be appreciated.

Thanks,
Phil