>Hi All,
>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,


Retry?

Something like:

fl_error = .t.
DO WHILE fl_error
   TRY
      * Your code goes here
   CATCH
       fl_error = .f.
  ENDTRY
ENDDO

You could use a transaction (IF you need it) and adjust code for your needs (you may want to have a 5 attempts and then just go to the next statement).