What Kevin said, but in the opposite chronological direction, looking back instead of forward. (We do have a forecasting and analysis and price list management module, but history is simpler than that.)
In our vertical, order details have individual rows for each: items, quantities AND THEIR PRICES. So, if you ever sold an item, you know the price, when. And if you didn't sell any? Well, how much does the price matter then? Easy-peasy. No data change. On Tue, Apr 23, 2019 at 2:10 PM Kevin J Cully <[email protected]> wrote: > I'm going to reply but in a different direction. Yes, this approach might > require a DBA (or data structure change). > > I'm currently working on a system that has Pricing Calculation rules. > These rules can be configured ahead of time to go into effect at a future > date. For example, you can schedule 2020 pricing by entering the new > calculations with the go-live date of 1/1/2020. > > Here is the key question: Is this a feature you should add to your > product? By allowing them to schedule their price changes, and not > deleting any history, they can get the best of both worlds in seeing what > happened and also scheduling what will happen. This would be dependent on > a new pricing table per product, and some new maintenance screens. > > Worth it? > > > -----Original Message----- > From: ProFox [mailto:[email protected]] On Behalf Of MB Software > Solutions, LLC > Sent: Monday, April 22, 2019 3:34 PM > To: [email protected] > Subject: How best to do an audit trail of changes (EASILY WITHOUT THE NEED > FOR A DBA) > > 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/cacw6n4ufl5x30mzeuo4sxa1jmxmj4xtptq++ku2v8p3fhdt...@mail.gmail.com ** 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.
