03-23-2018, 05:34 PM
Well, as you may recall from some earlier discussions, my database version is 40. It has been refusing to update for a long while, so the theory that it is now definitely missing crucial tables seems sound. I usually update MSPro with every release, so I'm sure I didn't have a malfunction with 2.1.1. (I'm currently at 1.9.6, since that was the easiest to restore. Otherwise I would have gone back to 2.1.1.)
I assume that when MSPro loads the database and detects an old version, it tries to perform an upgrade? And that this, at least partially, succeeds since (if I recall correctly from earlier discussions) my database contains at least some of the post-40 tables.
Wrt. the disk/file access: The older MSPro opened the previous location, the newer MSPro did not, but that may be due to the fact that I made a clean install.
I assume that when MSPro loads the database and detects an old version, it tries to perform an upgrade? And that this, at least partially, succeeds since (if I recall correctly from earlier discussions) my database contains at least some of the post-40 tables.
Wrt. the disk/file access: The older MSPro opened the previous location, the newer MSPro did not, but that may be due to the fact that I made a clean install.
Johan
johanvromans.nl — hetgeluidvanseptember.nl — mojore.nl -- howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 13.0, AirTurn Duo & Digit (Gigs).
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (maintenance and backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).
johanvromans.nl — hetgeluidvanseptember.nl — mojore.nl -- howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 13.0, AirTurn Duo & Digit (Gigs).
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (maintenance and backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).