PetrCBR wrote: ↑Tue Jun 16, 2020 2:06 pm
It will be fixed in next build.
Petr, some feedback regarding your responses.
Your minimalist responses make it difficult to have much confidence that you have understood what has been reported. Could you at least include a link to Mantis tracking of issues?
I am sensitive to this issue because it has damaged my MM4 database (again!), and it has been difficult to get any proper buy-in from MM, or understanding of what I am reporting, in this thread regarding this issue.
There is a saying about injury one receives:
The 1st time it should be seen as an accident.
The 2nd time is could be seen as a coincidence.
But the 3rd time it should be seen as negligence.
This is the 3rd time that this bug, or one very like it, has damaged my MM4 database, when I should be protected by using MM5 beta in portable mode.
I reported the bug for the 1st time in February 2017 here
, where you reported it as fixed.
I am sure that you appreciate that it is not much fun having to recovery your production database from backup. This time I needed to restore to the 5th of June.
And I don't understand why you seem to care so little about people's databases, that you don't pull the most current version of MM5. Surely if will screw up MM4 databases for anybody who has that database in a custom location?