>The INSERT-SQL and APPEND BLANK both use a header lock. As Boris suggested, you can retry insert on error. It could be easier to do in the class Error event where you can check for Error=108 and issue RETRY. You may want to put a short delay before doing that and limit the number of retries.
>

Interesting, we may try to adjust our classes logic for that, because that's the error that's been bugging the system for a while.

>>I have a LAN-based desktop application I have implemented an audit logging class for. It creates a lot of records in an auditlog table for all changes made to the tables opened in a form when the user saves. I'm getting error 108 on the INSERT-SQL command due to collisions when several people are active at the same time. I'm aware of the table locking that happens when INSERT-SQL runs, and also that a table header lock will still happen if I substitute APPEND BLANK.
>>
>>I'm looking for a good strategy to handle this table locking collision my audit log class code. If I out the INSERT into a TRY-CATCH structure, what do I do in CATCH section?
>>
>>thanks,