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" <[email protected]> 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] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
