I have an audit trail for field modifications system incorporated in one of my databases. I'm using what appears to be the standard method of doing this type of operation in FM.

The trigger for the generation of the audit trail is as follows:

A unique serial number field

A calculation field that has a case statement which includes all the fields you want to track.

A self join relationship between the two fields above.

A current info field. Which is a calculation using the status(CurrentDate), status(CurrentUser) Status(CuurentFieldName), Status(CurrentFieldContents) etc..

A history (log) field that is a does a look up on the field below.

A calculation field that adds the current info field and the history together.

It all works fine apart from on a couple of fields that I'm tracking, I have a field validation (by calculation) on these two fields the history is entered twice into the log. FM seems to trigger the look up twice (when you exit the field) on the current info field because it is having to perform a validation. Not the end of the world, but I can't seem to come up with a decent work around.

Cheers

Andy

Can you Stuff and attach a sample of your file?