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, datades@adam.com.au 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.