Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
From: Stéphane Charette <stephanecharette@gm...> - 2008-12-30 19:54:31
|
> after having tried to find some help on the website, I'm still unable > to solve the problem on my own. As it's not just me, it would be good > to know if others had no problem with migrating their data, and if > so, which version they did use. Maybe I get a hold of that version > and can check it out. If you're not getting a response to this on the GRAMPS-USERS list, it may be time to take it to the developers list instead. Also, you should know that a lot of the active developers are currently away due to Christmas seasons. Where I've personally seen this problem before is someone trying to load a grdb database after they've blown away their .gramps folder, or they copied the .grdb file to a new computer without realizing they also need the database environment in .gramps. This problem only exists in GRAMPS 2.2.x and below. The newer versions of GRAMPS 3.x has changed how family trees are stored specifically to avoid this problem. (http://www.gramps-project.org/wiki/index.php?title=Recover_corrupted_grdb) But if I remember correctly, you were trying to import an old GRAMPS xml database, is that right? Do you know what version of GRAMPS you used to create the xml? And what version you are trying to import into? Lastly, if you're OK with sending me the .xml directly (not posted on the list) and you are trying to import into 3.x when you get the error, I'll see if I can fix the error for you. I've got some time today reserved to work on GRAMPS. Stéphane |