If the tables are in a DBC, you can always create an Insert trigger for them. Put the trigger code in the DBC's StoredProcedures. Then put a function call to this SP in the tables' Insert trigger property. In the stored procedure, I would have code that populates an audit table with information from the call stack, table being updated, date and time of insert, UserID, and workstation.

>Hi,
>I am working on a simple program which is used for registration of laboratory samples from up to 7 workstations at the same time. To check if a sample is already registrated I us. IndexSeek (cStr,.F.,ALIAS(),'parti') to check without moving the record pointer. If found, it does a TableRevert() and moves to the duplicate. This seems OK for most of the time, but for some reason there is a couple of blank records among hundreds each day. And worse, a few records are filled with bars. The program has 4 other forms which is used to do lookup and update data as the sample is processed. There is only one table involved. Table buffering is 3 in dataenvironment and data session is set to Private in each form.
>
>How can I find where the blank records comes from? (I should like to have an event that fires when/before data is stored)