After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 565373 - Import of 1.8.x file has incomplete data on Windows
Import of 1.8.x file has incomplete data on Windows
Status: RESOLVED INCOMPLETE
Product: GnuCash
Classification: Other
Component: Import - Other
2.2.x
Other Windows
: Normal major
: ---
Assigned To: Andreas Köhler
Christian Stimming
Depends on:
Blocks:
 
 
Reported: 2008-12-22 19:18 UTC by Norbert Enzinger
Modified: 2018-06-29 22:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Norbert Enzinger 2008-12-22 19:18:53 UTC
I used gnucash 1.8.1 on Linux Red Hat for the last years. Now I want to switch to my other computer which have Internet access. It's running Windows XP. I installed gnucash 2.2.8 sucessfully and opened the file generated on the linux machine. The tree of all accounts was imported properly, but no single value is imported!
Comment 1 Christian Stimming 2008-12-28 20:51:32 UTC
I'm afraid the jump from 1.8.x to 2.2.x is not any longer supported. Due to limited developer resources only the upgrade from 1.8.x to 2.0.x and subsequently from 2.0.x to 2.2.x is supported. To re-use your old file you most probably need to get a hand on some Linux computer where you need to install a gnucash 2.0.x version, then open and save the old file, and then use that one in 2.2.x. Sorry for that.
Comment 2 Norbert Enzinger 2009-01-01 14:30:46 UTC
(In reply to comment #1)
> I'm afraid the jump from 1.8.x to 2.2.x is not any longer supported. Due to
> limited developer resources only the upgrade from 1.8.x to 2.0.x and
> subsequently from 2.0.x to 2.2.x is supported. To re-use your old file you most
> probably need to get a hand on some Linux computer where you need to install a
> gnucash 2.0.x version, then open and save the old file, and then use that one
> in 2.2.x. Sorry for that.

Thanks for this information!
One more question. Is there a chance to send my file to one of the developer for convertion? I really would appreciate this support, since I'm not able to install 2.0.x on one of my computers! Nevertheless I really would like to keep my old data in future.
If possible please let me know address!
Norbert
Comment 3 Christian Stimming 2009-01-04 21:14:45 UTC
I think I can compile a 2.0.x gnucash here. Contact me directly if you want to send your file to me. 
Comment 4 Christian Stimming 2009-01-24 09:33:21 UTC
For the record: Norbert has sent me his 1.8.x file. I imported this in 2.2, which brought up the "mixed character encoding" dialog. Indeed there were both UTF-8 and ISO-8859 strings in the file, but it was easy to choose the correct ones. I then saved from 2.2 and sent Norbert the result and all is solved.
Comment 5 Christian Stimming 2009-02-25 09:10:48 UTC
And again for the record: Other people have reported a similar issue when trying to open a 1.8.x file (Linux, because nothing else was available in 1.8.x) with 2.2.x on Windows.

Apparently the Windows import wizard for older gnucash files (1.8.x) doesn't seem to work as intended (probably due to the mixed character encodings). Only on Linux it works just fine. The workaround in this case is to open and save the 1.8.x file with 2.2.x on Linux, and then continue on Windows.

I'll leave this bug open until a resolution can be found on Windows, or until no-one has a 1.8.x file around anymore (heh).
Comment 6 Andreas Köhler 2009-02-25 20:16:33 UTC
Maybe I should take a look at this...

BTW, I have never tested that feature on Windows because it did not seem to be necessary anymore.
Norbert, if you do not mind, feel free to send me your data file per mail, e.g. gpg encrypted, then I have something real worldish to work with.
Comment 7 Andreas Köhler 2009-03-01 00:25:19 UTC
BTW, my first tests all succeeded, so I indeed need some data to work on to improve that dialog.
Comment 8 Akhil Laddha 2009-12-31 10:56:03 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 9 John Ralls 2018-06-29 22:14:34 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=565373. Please update any external references or bookmarks.