I have had Legacy crash on me 3-4 times when I have accidentally clicked too soon after the previous click, but that is a different issue, I believe, and one I can live with as it occurs infrequently and (as you say) there appears to be an obvious "trigger" for it. It doesn't give the 3021 error.
Pete On 30 May 2015 at 17:32, Brian L. Lightfoot <[email protected]> wrote: > It happens to me quite frequently. The good news is that you don’t lose > any data but the abrupt close of Legacy causes it to forget where it was > and will re-open to the person that was last on your previous closing of > Legacy. I have determined what makes it happen for me and how to avoid it. > All it takes is a too quick click of the mouse on the new Edit Event window > that just opened without waiting an obligatory second or two for the > programming to catch up. It only started to happen with version 8 which > seems to be noticeably slower in many calculations especially in > relationship calculations and web page creation. This error will probably > never happen under the old version 7.5 but seems to plague version 8.0 > quite noticeably especially if you are so proficient with the mouse and > movement, knowledge of the layout of the new window that is about to open, > and too quick to click on a particular button in the new window. > > > > For me, the solution was to train my mind to count 1-2-3 while the program > catches up and then click on whatever button you want. I have what I would > consider a relatively fast processor, 2.2 GHz Dual Core, so I’m not so sure > we can blame processor speed. And while I use version 8.0 of Legacy, I > still have version 7.5 on my system just for the sake of occasionally > testing something or looking to verify just how something changed. Using > the nearly exact same database, I cannot force that error under v7.5 but I > can under v8.0. > > > > I’m not exactly sure if this is what is happening to you because you > stated that you were using the TAB key after entering some data. For me, it > seems to be merely opening the window and then too quickly clicking on a > button. When I pause on the window, then the error never happens. As a > programmer you would know what I mean when it seems as if “Garbage > Collection” were occurring and my click on a button before 2 or 3 seconds > seems to catch the program by surprise. > > > > As you stated, you’d think the Legacy programmers can trap this error but > they don’t seem interested until enough users complain. The problem is that > the error is not easily reproducible, therefore the programmers are not > going to waste any time for an error that happens to only a very few users > and only under special conditions. > > > > That’s my opinion and I’m sticking to it. > > > > > > Brian in CA > > > > > > > > *From:* Forefathers Research [mailto:[email protected]] > *Sent:* Saturday, May 30, 2015 5:34 AM > *To:* [email protected] > *Subject:* [LegacyUG] Run-time error 3021. No current record. > > > > 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/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > 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/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ 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
