The solutions on the website *always* apply to the error number that they're linked to and are the solutions we have found that usually resolve the issue.
The steps on the website don't say to compact - they're 1. Repair Legacy by installing the update again 2. Reset the temp folder 3. Run check/repair and if those steps don't work 4. Export to a new Family FIle. Running Compact Family File is always a good idea to help keep your file a smaller size. Check/Repair compacts it a bit but Compact Family File gives it a bit more compression by cleaning up "empty spaces" within the file. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Apr 12, 2012 at 10:35 PM, Jan Roberts <[email protected]> wrote: > Well, I’ll go He for tiggy! I was having trouble with an Error 3021 which > didn’t appear to be related to the Solutions By Error Number suggested. > Today I remembered about Check/Repair (don’t often have to resort to it > thankfully) so decided to give that a try. Sure enough, it found the Error > 3021, but suggested I run a Compact File when Check / Repair finished. I > did, and voila the troublesome record was repaired without me having to do > anything, according to the Error Log that popped up after I finished. So, > all’s good. However, my other problem of Event Pictures not sticking has > also been ‘cured’, so I’m a happy little camper. > > Cheers > Jan 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 Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
