- #Legacy family tree support driver
- #Legacy family tree support software
- #Legacy family tree support windows
That can of worms probably deserves a separate post! I am now going through the tedious process of cleaning up – changing the christening facts back to baptism, fixing up the place list, changing the census (family) fact to a shared census fact, etc. But all in all, I think (hope) that I’ve made the right choice – for me, for now. On the other hand, there are certain things that Legacy has that I miss – like hovering the mouse over a child in the family view to see the spouse list and all the shortcut mouse clicks. I am also liking the interface now that I’ve been using it for a couple of weeks. Sadly, RM does not support shared source citations, but shared facts are a step in the right direction.Īnd what about tagging – the lack of which stopped me from switching to RM all those years ago? I have found that the named groups give me about 80% of the functionality of tagging - and I can live with that. RM did an excellent job implementing shared facts in a very flexible and powerful way, including user-definable roles and sentence structures. For example, a baptismal or christening fact can be shared with the godparents and even the officiating clergy.
(Or my work-around which was to create the census event as a marriage event and basically ignore attaching it to the children.)Īdditionally, shared facts allow for the capturing of relationships beyond spousal and parent/child.
#Legacy family tree support software
As a software engineer who specialized in database design, I personally feel this implementation is much better than having multiple copies of the event – as Legacy would have you do. First and foremost, this feature allows you to create, for example, a single census event/fact and have it attached to all the members of the household. The more I looked into RM’s implementation of shared events – or as they call it, shared facts – the more I decided it was a must-have. These 2 pet peeves, coupled with some other minor annoyances, caused me to really give RM a good look when I got the email about their Version 6 release. It still doesn’t support shared events, and, as I blogged about before, it also doesn’t support shared source detail (citations). After evaluating the competition, I decided to stick with Legacy and hope shared events would be addressed in the next release.įast-forward about 7 years. My perception was that RM did not support tagging, and that was a Legacy feature that I did not want to give up. We (the users) were told that the programmers wanted to include it, but it required too much “restructuring.” At that time I looked at RootsMagic as well as other products. The first time that I took a close look at the competition was when Legacy V6 was released without the much anticipated “witness” feature which would have provided for shared events. So I decided it was time to take another look at the competition to see if there was a better fit for me.
But lately I have been feeling an ever growing disconnect between the features I want in a genealogy program and what Legacy provides. After using Legacy Family Tree since 2004, I have decided it’s worth the pain to switch to RootsMagic.ĭon’t get me wrong - Legacy is a great program.
#Legacy family tree support driver
My Family Tree 64-bit because no native 64-bit database driver is available and JET2 database file structure is undocumented.I am in the processing of doing something that I never thought I would do - that is porting my genealogy database to a different software package. Legacy 2 files use the JET2 database format (this can be opened in My Family Tree 32-bit, Access 2.0 through Access 2007, any version of Legacy, or using the JET4 database driver on 16-bit and 32-bit versions of Windows).
#Legacy family tree support windows
Legacy Family Tree running on Windows 95. Of the files in the same folder as the database file or a subfolder nextįig 1. To automatically import multimedia files, place a copy Them after the import, or you can resolve them at any time in the Any links to online files or files which cannot be located willīe imported as place holders. They can be found on the local disk at the location the link points
Stored in other locations. Files are automatically imported if The database file may contain links to multimedia files Legacy 3+ stores data in a JET4 database which is a single file with a *.fdb extension. Created by Legacy Family Tree versions 2 and later can be
0 kommentar(er)
