On 5 Feb 2006 at 15:34, Gary Crull wrote: > Gary, > > When I first read your inquiry and saw your name I thought I might have > been writing to myself! I have a similar issue. > > I've kept an Access database of scraps of source(s) information for > years...long before I switched to Legacy. One of the reasons I switched > to Legacy was that it was better at presentation of my genealogy > information AND retained my ID#'s when I imported the GEDCOM file from my old > program. This was of PRIME concern since my Access DB is maintained for > information based on the ID#. I presently have close to 3,000 bits and pieces > of information entered from Internet sources, books, obituaries, newspaper > entries, wills, war records etc. > > My problem (dilemma?) is that I have all this source information in an > axillary database but as far as my knowledge is concerned no way of > getting it into NOTES in the individuals ID# in Legacy short of > transcribing it by hand....which I'm not about to do - given the amount > of duplicate work that would cause. > > In addition to the ID# in the Access database each record has a unique > Reference number (0001-2875). To illustrate, ID# for ancestor > great-grandfather Jacob Killbottom Legacy ID# 193 and ID# 193 in the > Access database has reference numbers 0017, 0989, 1712, 2276, and 2301 of > various pieces of information I've found for Jacob Killbottom. What I'd like > to know is if there's some way of *linking* the Legacy ID# with the ID# in my > Access database.
I have a similar concern. Long before I started to use Legacy I used a program called Family History System (FHS) to enter my family history on computer. Then I bought PAF 2.2, mainly because it came with a program called the Research Data Filer (RDF). The RDF program keeps track of pagar files by indexing them. Every document is given a number, and is filed in numerical order. RDF has two files - .DOC and .DAT. Ther DOC file is simply a description of the paper document, which may be a book, a letter, a copy of a will, a birth certificate, a transcription of an interview (or a reference to a taped interview), a photocopy of a directory page. The DAT file is an index to persons mentioned in the documents -- it has the Document Number, the person's name, sex, Id (RIN), the event, the date of the event, the place of the event, relations of the person, and the Id numbers of these relations (there is space for 3 numbers) and comments. When I transferred my data to Legacy (and I still enter it first in FHs, and copy it to Legacy when I have about 50 or so new entries) all the RINs remained the same (well, not quite - Legacy scrambles them on GEDCOM import, so I use PAF 4 as an intermediate program, and then Legacy keeps them straight). I've now been looking for a replacement, or at least a supplement for the RDF files. I've been using them for 15 years, but the were designed for MS DOS, and many modern printers don't seem to handle MS-DOS files and programs. While they can "focus" on entries for a person (using the RINs), and sorted by date to give a rough chronology of a person's life, I've felt I need opf more versatile "event" program to be able to analyse such things. I've been trying to discuss this in the soc.genealogy.computing newsgroup, but most people don't seem to know what I'm talking about, or see the need for such a thing. What I want is to get some of the "person" information from the Access files, including the RIN/Id, name, date of birth and death, and notes, and then link this to other tables and other persons to create an event database. There would be and Event table in a many-to-many relation with a Person table -- one person participates in many events, one event may have many participants. So the Event table would be linked to the Person table by a "Role" table describing the person's role in the event - this would have the Id number of the Event, the Id number of the person (not the RIN from Legacy, which would simply be in the Person table as an extra field), the role of the person in the venet (Category and description), For example if the Event is a marriage, the role could be bride, bridegroom, witness, officiant etc. If the event is a crime, the role could be perpetrator, victim, witness, etc. To achieve this, it would be useful to be able to export certain fields from Legacy and to import them to the Person table of the "Event" program, rather than having to enter the data twice. -- Steve Hayes E-mail: [EMAIL PROTECTED] Web: http://www.geocities.com/hayesstw/stevesig.htm Phone: 083-342-3563 or 012-333-6727 Enter the drawing for a FREE Legacy Cruise to Alaska or a FREE research trip to Salt Lake's Family History Library. Open to users of Legacy 6 Deluxe. Enter online at http://legacyfamilytree.com/FreeTrip.asp Legacy User Group guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
