Originally Posted by Ronnie
I'd encourage you to look at how the "Relational" information is held together at the back end before making a claim that changing the front end was "easy"

Re-Writing would be doable but long-winded, but the real challenge would come in validating that the SQL Tables & Fields changes didn't end up corrupting User's Libraries when it was rolled out to Users'.

It's this last point that I believe will be the ultimate stumbling block to us seeing a true Track Level Sooloos implementation that will not involve a quite laborious Export and then Import into a new Architecture
I really don't see how this would be a "laborious" process.
I'd think the vast majority of Sooloos owners back up their data.

So any major update could/has to be tied in to a system update followed by a reload of the users data. The trick would be how to do this with the appropriate warnings to the end user. That's easy. The opening window: "DO NOT INSTALL THIS UPDATE UNLESS YOU HAVE A CURRENT BACKUP OF YOUR MDS SYSTEM ON AN OUTBOARD DEVICE! YOU WILL NEED TO RELOAD YOUR DATA AFTER THIS UPDATE IS INSTALLED. THIS UPDATE ERASES YOUR COMPLETE SYSTEM! IF YOU DO NOT UNDERSTAND THIS, PLEASE CONTACT YOUR Meridian DEALER OR GO TO THIS LINK FOR INSTRUCTIONS" Next window:" DO YOU HAVE A CURRENT BACKUP? YES (check) PROCEED, NO (check) CANCEL UPDATE"
Another way would be to charge for the update with appropriate warnings.

Done deal.
Now, M, rewrite the software.