Nancy, Go to our website at http://www.LegacyFamilyTree.com/Help.asp > Solutions by Error Number, where you'll find a solution to this error message. Thanks for using Legacy. Sherry Customer Support Millennia Corporation Support@MillenniaCorp.com http://www.LegacyFamilyTree.com We are changing the world of genealogy! When replying to this message, please include all previous correspondence. Thanks. -----Original Message----- From: Nancy Beck [mailto:naneki35@yahoo.com] Sent: Thursday, May 05, 2005 8:24 AM To: LEGACY-L@rootsweb.com Subject: [LEGACY] Error message Today I started getting error message No. 3021. Error getting next deleted RIN. No current record. What does this mean?? Can anyone help. Nancy

To Sherry and Dave and others with GEDCOM problems I am a former Generations user who converted to Legacy but found that Legacy has BIG problems with a Generations GEDCOM file. My problem was so bad that I was considering staying with Generations even though I had purchased Legacy. The problem was: Generations sources did not get into Legacy. My ultimate solution was to edit the Generations GEDCOM file, a task that took me over eight months to do. Fortunately, GEDCOM files hark from the old days of computing and are text-based (ASCII) so any text editor will do the job. I'll outline some of the details of my editing but first, I must apologize to Sherry and Dave for impugning the Legacy GEDCOM algorithm. It is not Legacy but Generations...they really screwed up their GEDCOM. No wonder Sierra is out of business. Here are the highlights of my editing. 1. Many of my sources got tagged as SSN even though I don't have any social security numbers in my database. The following was a real problem 1 BURI 2 DATE 23 MAR 1880 2 PLAC Clipperton Cemetery, W Nissouri Twp, East Middlesex, Ontario 2 SOUR @S21@ 1 SSN @N155@ All SSN tags had be changed to SOUR. In doing so, I had to be very careful to preserve correct numbering (e.g. SOUR @S1145@ must have a 0 @S1145@ SOUR at the end to refer to). If Legacy cannot find a referenced source, it stops dead. My editing method was to change a few source numbers then import into Legacy as a test noting total number of names and families. If Legacy stopped, I had to go back and rework the sources. The above was changed to 1 BURI 2 DATE 23 MAR 1880 2 PLAC Clipperton Cemetery, W Nissouri Twp, East Middlesex, Ontario 2 SOUR @S21@ 2 SOUR @S11155@ 2. Another error in Generations is the construct 1 DEAT 2 DATE 6 DEC 1990 2 PLAC Hugo, Lincoln Co, Colorado 2 NOTE In Lincoln Community Hospital 2 SOUR @S47@ Legacy simply brings this source in as a note. This had to be changed to 1 DEAT 2 DATE 6 DEC 1990 2 PLAC Hugo, Lincoln Co, Colorado 2 SOUR @S47@ 1 NOTE In Lincoln Community Hospital But you must be sure the SOUR numbers are the same in the beginning as in the reference area at the end of the GEDCOM file 3. Once the source tags and the note tags were interchanged I had the big problem at the end to change this 0 @S28@ SOUR 1 TEXT Clipperton cemetery, W. Nissouri Twp, Row 15 North; (description 1 TEXT of gravestone, white marble, badly worn, cracked); "In memory of 1 TEXT Edward Kearn/died Jan. 19 1876 ae 87 yrs/native of Co. Wicklow, 1 TEXT Ireland to this 0 @S28@ SOUR 1 TEXT Clipperton cemetery, W. Nissouri Twp, Row 15 North; (description 2 CONC of gravestone, white marble, badly worn, cracked); "In memory of 2 CONC Edward Kearn/died Jan. 19 1876 ae 87 yrs/native of Co. Wicklow, 2 CONC Ireland (CONC means concatenate). 4. Note that with the above changes, Generations sources still get into Legacy as just "Text" or "Output" so you've still got the job of manually creating titles, etc in Legacy. I was not able to construct a proper GEDCOM to do it. The above is all very tedious work and it took me forever and I only have 1042 names in my file. Those people who have 3000 or 7000 names would find editing a GEDCOM an impossible job I would think. I hope this helps but I think old Generations users are not going to be very happy because there is no easy solution to getting all of your data into Legacy. I'm a happy user of Legacy now but I still face the updating of every source, at least to get a correct source title in place. -- Dan Cooley