Retrying N times will reduce probability of the error but cannot eliminate it. You shouldn't leave the error unprocessed or you may miss some audit records w/o even knowing it.
Also you should check for the error code in the CATCH and act on 108 only otherwise you may hide other errors.

It's easy to put this table in SQL Server if you have SQL Server and know how to work with it. :)
The SQL Server wouldn't have problem with concurrent inserting the records.

>Thanks for the suggestions. Something like this would try a max of 5 times with a short random delay between tries. I'm still not doing anything about it if it eventually fails, but I assume this would cut that probability down considerably.
>
>I'm not using a back end database right now. I wonder how hard it might be to put just this audit table into SQL Server. Could that problem be avoided by doing that?
>
>
>

>Declare Sleep IN Win32API;
>INTEGER dwMilliseconds
>Local i, loError
>loError = .F.
>For i = 1 To 5
>	Try
>		Insert Into Auditlog_sys ; && etc 
>			
	CATCH TO oExp WHEN oExp.ErrorNo = 108
>		loError = .T.
>		Sleep(Rand()*50+10)
>	Endtry
>	If !loError
>		Exit
>	Endif
>Endfor
>
>