True... reminded me of the days when I needed to fix the Y2K bugs in a MIS system based on Foxpro/DOS back in year 2000.
Luckily, nothing went wrong! BUT then, there was no change to the database! :) On Sat, Jun 16, 2018 at 7:20 PM, <[email protected]> wrote: > Or an even simpler approach of 'if it aint broke, don't fix it'. > Particularly in legacy systems where documentation is out of date or missing > and some code does things you don't necessarily understand, just don't touch > it. -- .~. Might, Courage, Vision. SINCERITY! / v \ 64-bit Fedora 25 Server Spin /( _ )\ http://sites.google.com/site/changmw ^ ^ May the Force and farces be with you! _______________________________________________ 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/CAGv=mjdskvlbbqwerov3p6+pjuqunk8rk8r+dt74byr46kd...@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.
