Legacy is somehow associating an individual with a Source Detail via Id's in some table someplace, right? The only difference I really see is that Legacy forces a copy of Source Detail, so that each association has a brand new ID that ties them together. If you read that info. I pointed to, FTM also allows for this via their "Copy New Citation" (or something close to that). However, they offer the additional option of "Link to existing" which instead of copying and making a brand new ID, allows multiple individuals to be tied to the same source ID.
The way I see it, Legacy is forcing a one-to-one, while FTM allows for both one-to-one and one-to-many relationships with source details. Basic DB stuff. On Tue, Apr 13, 2010 at 3:04 PM, Dennis M. Kowallek <[email protected]> wrote: > Never having used FTM, I wonder if they have the equivalent of what > Legacy calls a Master Source. > > In Legacy you have: > > FACT <------>> SOURCE DETAIL <<------> MASTER SOURCE > > How would you depict what FTM does? > > FACT <------>> LINK <<------> SOURCE CITATION > > Is there a something in FTM that groups similar citations together? Or > is the grouping implied by what you enter in the citation. > > Maybe a knowledgeable ex-FTM user can jump in here. > > The reason I am asking this is that I wonder if the difference is that > Legacy chooses to store user data in the link table (SOURCE DETAIL) and > FTM doesn't. > > Anyway, it is interesting to see how others have attacked this problem. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
