Seems like the reversal would be a logged event as well.
I've always thought direct edits to any log by a user or even an admin corrupts the integrity of the log and invites unlogged edits to be made. Asking for trouble depending on the critical nature of the data changed.
Paul H. Tarver
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Frank Cazabon Sent: Monday, April 22, 2019 4:21 PM To: profoxtech@leafe.com Subject: Re: How best to do an audit trail of changes (EASILY WITHOUT THE NEED FOR A DBA)
If your clients are anything like my clients, make sure you allow them access to change the historical dates after they've changed the price. Someone is bound to change the price at the wrong time and need to go back in and adjust it.
On 22 April 2019 15:33:48 GMT-04:00, "MB Software Solutions, LLC" mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
VFP9SP2 app, MariaDB 10 (MySQL) backend.
One of my clients asked about a history of price changes. Easy enough to implement programmatically for the few price fields, but then I got to wondering if simply putting code in the ON UPDATE trigger to send the old record to a "history" table would be a more complete (and long term
EASIER) solution, whereby my app would query the "history" table for changes.
Your thoughts for tracking price (or other) changes?
tia, --Mike
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[excessive quoting removed by server]