After upgrading to 5.1 the 5.0.9 data file cannot be opened

Asked by Mark

I have been using 5.0.9 without problems.
I upgraded to new 5.1 release
HomeBank crashes as soon as it starts
The problem appears to be in the data file
When i remove the old data file it starts fine with a new data
How can i use HomeBank 5.1 with my data file which was created in 5.0.9??

Question information

Language:
English Edit question
Status:
Expired
For:
HomeBank Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Maxime DOYEN (mdoyen) said :
#1

If possible, downgrade to 5.0.9 open your file and anonimize, then send to hb email address
available here http://homebank.free.fr/support.php

If the problem is into your file, I can't help without that file.

Revision history for this message
Mark (k-mark-2) said :
#2

Thank you - I just sent you anonimized file to your email address. Appreciate your help.

Revision history for this message
Launchpad Janitor (janitor) said :
#3

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Revision history for this message
Mark (k-mark-2) said :
#4

It appears the question has expired, but I provided anynymized data and are still struggling with this. Can you help? thanks

Revision history for this message
Mark (k-mark-2) said :
#5

Hello, I have upgraded to version 5.1.1 and the problem still occurs when opening my 5.0.9 data file in the new version the application just crashes. I would really like to take advantage of the new features but cannot and have to keep using 5.0.9. Is anyone else having the same problem or is it just me?? Any help is appreciated.

Revision history for this message
Launchpad Janitor (janitor) said :
#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Mark (k-mark-2) said :
#7

After hours of going through my transaction data one by one I found that my data file included bunch of internal transfers to an account which was not existing. For some reason this never was an issue in 5.0.9 but as soon as I upgraded to 5.1+ the new code was crashing when it encountered transfer to account which does not exist.

You may want to handle it in the code more reliably. (just deleting the orphaned transactions or informing the user to clean up)

Revision history for this message
Luetyk (luetyk) said :
#8

Hello, I was affected by exactly the same problem (segfault) with 5.1 version. It happened with all 5.1.* versions, on Windows 7, Os X 10.8 and Unubtu 16.04.
The solution was exactly as what you gave in answer #7. I had one internal transfer from non existing account. Atfer it had been removed, everything worked fine.
Thank you very much for your explanation! I think that this should be mentioned somewhere in the main faq.