Yes, you are correct, this is how I see it.
@Tut Neither of us said that. No-one was talking about opening old data with new versions of manager.
My statement was that when you make a backup, you must also save a backup of the version of manager you used to create that version of the database file AND tie it to that data file.
The integrity of the user entered data relies on that.
@mauroskov was restating that, to which you commented about restoring older backups with newer versions. No-one is talking about doing that. In fact, I am stating exactly the opposite.
Explicitly, what I am saying is:
if you open an older backup with a newer version of manager, it will convert and now most likely show different data to what you are expecting from that backup!
I can not emphasis that enough:
opening older backups with newer versions of manager will most likely NOT present you with the same information you submitted to your accountant and the tax authorities of your jurisdiction.
For me this is a major issue because it is I that has to answer to any authority on the submitted data, not the software. Unless I can be sure the data previously presented by manager is consistent with what I entered, then I can no longer rely on it. And this is why I can no longer update the software, not without tools to verify the integrity of what I’ve presented.
I realise I will probably cop some flak for this opinion, but:
- When manager presents me information that I present to the tax office and for all intents and purposes, I believe that to be true… and then
- Manager changes my presentation of that data (through changing engines or report queries, whether I relied on bugs as features or not)
I do not believe I am the only one at fault. Yet, I will be the only one answering to the tax office.