- What OS are you using? *Windows * - What version of Windows are you using? *Windows 7 64-bit (up to date with latest updates)* - Do you use any Microsoft Office software on your machine and if so what version(s) are you using? *I have Office 2013 and Office 2010 installed, but mainly use Office 2013* - What version of Legacy are you using? *Legacy 8.0.0.499 (latest)* - Are you using the default settings for the Legacy family tree directories? If not, please explain what changes you have made to these settings. *Nothing changed*
Sorry, I don't have a spare computer I can test on as you suggest. Pete On 30 May 2015 at 18:24, Chris Seens <cseens1...@gmail.com> wrote: > I am a retired programmer also and I used to use MSAccess and Visual Basic > a lot. > > There are several very important questions before any possible solution to > this issue could even be considered: > > What OS are you using? > What version of Windows are you using? > Do you use any Microsoft Office software on your machine and if so what > version(s) are you using? > What version of Legacy are you using? > Are you using the default settings for the Legacy family tree directories? > If not, please explain what changes you have made to these settings. > > More questions will likely need to be asked once these questions are > answered. However, what I would do if possible, is to install the latest > and greatest Legacy version on a 'pristine' machine. Only Windows and > Legacy and restore your latest backup to this machine. Do you still get > this error? By doing this you remove any chance that there is some > conflicting software on your regular machine. > > Have a great day, > > Chris > > > On Sat, May 30, 2015 at 8: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 tur >> ning 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
