AddressBook Auditing - Z Tables

Has anyone figured out a good solution (without using 21CFR) to resolve the issue of records being written even when no data is changed? (just hitting the okay button records a change)

I need to send added and changed records to another system on a daily basis. Since just hitting the okay button writes a change record in F0101Z2, I could have tons of "invalid" records to process every day. And, you could have the same address book record out there many times all with the same date.

Any ideas? Thank you!
 
Michelle,
You might consider a DB trigger program. It can easily determine whether the 'main' part of the record changed.

Dave
 
There is a program called DB_Audit that you can attach the DB level trigger to the file and then only write out the fields you want when the fields you indicate change. We have it and it works well othe than some naming convention issues and poor reporting functionality.

Also if you read through the Z file and add the fields you are auditing to the break level you can create a work file before hand that has only changed records you want in it. Just an idea.
 
Back
Top