TOPIC:

I found a way to fix the problem.

Instead of converting your book form version 3 to 5, install version 4 and then convert your book with the conversion tool that this version provides. Then drop your book folder from version 4 into the /books folder of version 5. Run version 5 and do a year end and everything should be ok.

It seems that there is a problem when converting v3 books direct o v5.

I hope this helps others who might be pulling their hair out over this issue.

Hi,

I have just migrated my books form TC 3.7.54 to version 5. I used the conversion tool to convert my books, I then copied the folder with my book to my new machine running TC5.

When I open the book I get an error that my year end is 1899 so I try to do a year end and then I get the data integrity error:

"violation of PRIMARY or UNIQUE KEY constraint "INTEG_139" on table "TOTALS" on account9 Period 1"

I found this solution which suggests emptying the TOTALS table as it contains null values in the date fields:

www.osf-boekhoudpakket-administratie.nl/...error-violation-of-p

This doesn't fins the problem. When I open the book after deleting totals it seems the null values are re-created.

I have also tried running a data integrity check followed by re-calculating the totals. After completion I am able to run a year end, it says it was successful but every time I open my book it says the year end is 1899 etc.

Can anyone help, I've been using TC for many years but I can't afford to waste any more time trying to fix this. It seems the conversion process isn't 100%. After many years of problem-free use I would hate to have to search for a new product if TC5 doesn't work.

Thank you in advance.