Hi Pete, I'm not Sherry but a comment or two which may or may not be related.
The Event Sentence Definitions you show are the Legacy Default sentences. However, your use of the Description field suggests you need to edit the sentences. I edit them as I mainly have UK censuses and put the head of household in the Description field. I have a separate events for the few US and Canadian censuses I have. That wouldn't cause the error though. I can't recall if you said the error keeps returning if you export to a new file or only when you just do a check/repair. Many people work with their family file in a non default position without encountering this error. Why don't you work with Support direct since this is a persistent error for you but not for others? Cathy Forefathers Research wrote: > > Hello Sherry. > > I've been unwell for the last week, so not doing a great deal of work > in Legacy, but have just had the crash again, when entering a census > entry as an event. See screen print here: ​ > Legacy crash 2015-06-10.JPG > <https://drive.google.com/file/d/0B4YCMQXdrgkETkxncFl1VHYzaFk/edit?usp=drive_web> > ​ > As always, it occurred when pressing tab to move from the "Date" field > to the "Place" field. > > I ran File Maintenance. This is the error log produced, which is > always the same: > ​ > Legacy Error 2015-06-10.Log > <https://drive.google.com/file/d/0B4YCMQXdrgkEb0t4clRnZ0VIX2s/edit?usp=drive_web> > ​ > Here is the definition of the Census event. > ​ > Census Event.JPG > <https://drive.google.com/file/d/0B4YCMQXdrgkEMjJvYm1FNnlmeHc/edit?usp=drive_web> > ​ > Please let me know if you see anything wrong here or if there is > anything else you would like me to do to try to help diagnose the > problem. > > Could it be in some way connected to the fact that I store my Legacy > database files in a folder specific to each client, rather than in > Legacy's default location? > > Thanks > > Pete > > > > On 1 June 2015 at 15:30, Sherry/Support <[email protected] > <mailto:[email protected]>> wrote: > > Take a look at your personally entered Event Sentence Definitions and > make sure they're all using the correct replaceable fields and they're > formatted in a manner like the default ones. > > I don't think the sources are a problem since the error is when you're > adding or editing an event, but they could be if they're linked to the > events. > > Sincerely, > Sherry > Tec hnical Support > Legacy Family Tree > > > On Sun, May 31, 2015 at 4:34 AM, Forefathers Research > <[email protected] <mailto:[email protected]>> > wrote: > > 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< > BR> 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 > > > > 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
