https://bugs.kde.org/show_bug.cgi?id=368593

            Bug ID: 368593
           Summary: KmyMoney File Not opening and gives error As " Please
                    use an older vesion...."
           Product: kmymoney4
           Version: 4.8.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: NOR
         Component: file
          Assignee: kmymoney-devel@kde.org
          Reporter: somoor...@yahoo.co.in

I am using KmyMoney (in Ubuntu) for my personal finance managment since last 4
years, after migrating from a legacy made finance software. With almost 10 to
12 years of data, it was working fine. But suddenly it is not opening and
throwing the following error.
"File /media/paarkavin/Paarkavin/Ex1/YaArO/yAaRo - Sep-16.kmy contains the old
binary format used by KMyMoney. Please use an older version of KMyMoney (0.8.x)
that still supports this format to convert it to the new XML based format."
Recently i made upgrade from 15.1 to 16.04 so along with ubuntu i also made a
upgrade on KmyMoney from 4.7.2 to 4.8.0. 
After the upgrade, still it was working well for 10 days and suddenly it is
started giving the error. I tried with previous versions also (4.6.4) but the
error is repeating. Tried wthe same with windows version also. Still the same
error. In windows no upgrade has been made.
Please help to recover the data. how to solve this error and open my kMymoney
file.
2 years earlier backup kmy file i opened find it is opening.
Thanks in advance

Reproducible: Always

Steps to Reproduce:
1.Every time i open the file it is repeating
2.
3.

Actual Results:  
File /media/paarkavin/Paarkavin/Ex1/YaArO/yAaRo - Sep-16.kmy contains the old
binary format used by KMyMoney. Please use an older version of KMyMoney (0.8.x)
that still supports this format to convert it to the new XML based format.

Expected Results:  
Instead of opening the file it is throwing the error.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to