Hi, thanks for responding Sherry. Sorry about the attachment: point taken. As I mentioned, it's not just one file that gives this problem: I have many Legacy files for different projects, and any or all of them will give this issue at some point or another.
And the size of the file does not seem to be related either. As I mentioned, I had this issue recently within about 20 minutes of starting to input into a new, empty file. One thing that could be relevant, however, is that I always use the option to import sources from a previous file when creating a new file, to avoid the need to re-enter all my source definitions. Could that be a factor? It is certainly the case, I think, that the problem occurs more frequently when I am inputting an event where I myself have defined the event. Pete On 30 May 2015 at 14:27, Sherry/Support <she...@legacyfamilytree.com> wrote: > First of all, I'd suggest that you read the Guidelines for the Legacy > User Group - you'll find that we ask that you don't send attachments > to the list. Many of our listers are still on dial-up or are paying by > how much broadband they use plus due to the risk of hidden malware in > attachments we ask that attachments to the list not be opened. The > link to our guidelines is at the bottom of every email to the list. > > I can't remember the last time I personally saw Error 3021 when using > Legacy on any of my computers and I've been using Legacy for nearly 18 > years. It's also rare that we see that error message sent to Support > and for the vast majority of the few we see, the check/repair resolves > the issue. > > The one time I had it and the check/repair *didn't* resolve the > problem, I followed the second option in the Knowledge Base of > exporting to a new Family File. I don't think I've every had to > suggest the last option of exporting to a gedcom. > > "3. If the above steps fails to fix the problem, export your records > into a new Legacy family file: (steps snipped) > > "4. If steps 1-3 fail to fix error 3021, export your records to a > GEDCOM file and then import the GEDCOM back into Legacy. If you use > the SourceWriter to create sources, please be aware that your > SourceWriter sources will be converted to the Basic Source system so > do this step as a last resort. (steps snipped) > > "5. If all else fails, your only option is restore your family file > from your backup copy." > > > http://support.legacyfamilytree.com/article/AA-00291/11/Error-Messages-Problems/Error-3021.html > > I don't know what it is that's going on in your file which triggers > this error, but it's actually quite a rare occurrence. As a > programmer, you know how difficult it is to fix a "bug" that happens > very rarely and you can't duplicate. > > The real question boils down to asking what it is in your Family File > that's triggering this error and since you have found the steps, that > might be a clue to the problem. > > Have you ever manipulated the Family File in Access? Are the Events > ones that you've added? Have you changed the Event Sentence > Definitions? > > The data entry you're doing are generally not where the Error 3021 is > seen, but most commonly seen when clicking on the Name List or > Marriage List. > > Give the other steps a try and see if they resolve the problem. > > > Sincerely, > Sherry > Technical Support > Legacy Family Tree > > > On Sat, May 30, 2015 at 5:33 AM, Forefathers Research > <resea...@forefathers.co.uk> wrote: > > I am a professional genealogist. After over 30 years working in IT as a > > computer programmer, and over 25 years as an amateur family historian, I > > spent 6 years studying for a higher certificate in genealogy, before > turning > > full-time as a pro genealogist 3 years ago. > > > > So I feel I am a fairly good position to be able to judge Legacy as a > piece > > of genealogy software, both as a programmer myself and as a genealogist. > And > > I am a big fan of Legacy: I use every day of my working life, and choose > to > > use it in particular because I like its Source Writer system, the ease > with > > which I can keep track of my sources, assign sources to events and > produce > > reports. > > > > But there is one aspect of Legacy which absolutely drives me barking mad > and > > wastes a lot of my time every day of my working life, and that is the > > regularity with which Legacy crashes with the database error "Run-time > error > > 3021. No current record." See the screen dump attached - this happened > to > > me just a few minutes ago. This was the eighth time this has happened to > me > > so far today. > > > > Now, I know you will say "Ah. There's a fix for that". Yes, I know I am > > supposed to run File Maintenance, and I have dutifully run File > Maintenance, > > not once but twice, every time this crash has occurred. It will then go > away > > for half an hour or so, then come back again. > > > > This is not an issue with any particular Legacy file either. I run many > > projects simultaneously and have at least one Legacy file for each > project. > > This bug affects any and all of them. Recently, I created a new empty > Legacy > > file from scratch for a new project, then started inputting data, and > > experienced a 3021 crash within the first 20 minutes. So it's not just > > something that affects big files that I've been working on for a long > time, > > > > I have reported this issue to Legacy repeatedly but do not seem to be > able > > to get them to acknowledge that this is a bug. The view seems to be that > > telling me to run File Maintenance when it happens is acceptable. As an > > ex-programmer, I simply can't agree with that. I would be able to > understand > > it and sympathise if they were to tell me it was a bug they couldn't > find a > > fix for, but please don't try to tell me this is acceptable. It is the > one > > thing that would make me consider adopting a different genealogy > program, as > > it wastes so much of my time and causes me so much annoyance every single > > working day. > > > > I have Googled the database error itself and it does seem to be a > > commonplace Microsoft Access error (see > > > http://answers.microsoft.com/en-us/office/forum/office_2010-access/access-3021-error-no-current-record-found/5e37caf3-d243-41c5-904a-7d1e7c99c1e8 > ) > > which any reputable piece of software should be able to trap and handle > > without crashing, i.e. forcing a restart of the program. So if the > condition > > itself can't be avoided, surely Legacy should be able to detect it and > > handle it gracefully? > > > > Does anyone else experience this or is it just me? If it's just me, then > I > > suspect I'm using features that others don't very much. To be specific, > the > > error occurs: > > > > 1. Only when I am adding an event. > > 2. Only with some event types. > > 3. Always when I have just input something into the date field. See > screen > > dump attached: I had just entered a year in the date field and pressed > tab > > to go to the next field. > > > > Or is there some way to "encourage" Legacy to fix this? > > > > Thanks > > > > Pete > > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > > Archived messages after Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > > Archived messages from old mail server - before Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > > Online technical support: http://support.legacyfamilytree.com > > 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 > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com 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
