04-25-2022, 10:07 PM
OK, upon further examination I think it's due to a sync complication and so not the fault of MSP.
The updates changed the contents of the LocalState folder initiating a sync though. This seems to have resulted in a conflict with the db (though it wasn't changed) so it renamed it to "conflicted" and thus the db couldn't be found anymore by MSP at startup after the update.
I can think of an improvement though.
If you change the warning of the missing db though to 2 options like "do you want to look for the database" (or something) with the possibility to open a file manager window to examine the folder and choose/rename a file rather to just open the last backup file (which should stay the 2nd option) the user could fix the problem within the app right in the startup. Which is a good thing especially in a performance situation. Maybe you can consider that though it's probably a rare scenario.
Thanks.
The updates changed the contents of the LocalState folder initiating a sync though. This seems to have resulted in a conflict with the db (though it wasn't changed) so it renamed it to "conflicted" and thus the db couldn't be found anymore by MSP at startup after the update.
I can think of an improvement though.
If you change the warning of the missing db though to 2 options like "do you want to look for the database" (or something) with the possibility to open a file manager window to examine the folder and choose/rename a file rather to just open the last backup file (which should stay the 2nd option) the user could fix the problem within the app right in the startup. Which is a good thing especially in a performance situation. Maybe you can consider that though it's probably a rare scenario.
Thanks.