I'll try this next time the issue occurs Sherry, so probably tomorrow. My gut feel is that you could be on the right lines, and that the problem is likely to be connected in some way to modified or user-defined events in some way, as:
- that is certainly a feature I use, and other might not (which would explain why I seem to be plagued with it and others not) - the crash occurs when I am using that part of the system Thanks Pete On 30 May 2015 at 17:59, Sherry/Support <[email protected]> wrote: > Sorry - I should have added to *backup* the Family File (File > Backup > File) before resetting the Event Sentence Definitions to default. That > way you can restore the file with the edited Event Sentence > Definitions if resetting them doesn't help. > > To reset the definitions, go to File > File Maintenance > List Cleanup > and select "Event Definitions" under "Keep/Restore Original Values > for..." > > > Sincerely, > Sherry > Technical Support > Legacy Family Tree > > > On Sat, May 30, 2015 at 9:52 AM, Sherry/Support > <[email protected]> wrote: > > Tessa, > > > > My point was that if he edited the file in Access or changed Event > > Sentence Definitions, he *could* have done something that "broke" it. > > > > We do not recommend messing with the file in Access although many > > people do. Doing a simple query for a search shouldn't be a problem, > > but an update query could mess things up. > > > > With Event Sentence Definitions, you have to be careful on how you > > edit or create them, using the appropriate fields. > > > > If done right, there should be no problem with the Event Sentence > > Definitions. I'd almost recommend resetting them to defaults if he had > > edited them and see if the Error 3021 continues. > > > > > > Sincerely, > > Sherry > > Technical Support > > Legacy Family Tree > > > > > > On Sat, May 30, 2015 at 9:03 AM, Tessa Keough <[email protected]> > wrote: > >> I got this error twice a while ago, but I have not seen it recently. I > do > >> think if Legacy allows us to add events or modify sentences then that > should > >> not be a source of the errors (as mentioned by Sherry). Telling us we > can do > >> something with a program and then telling us that doing it might cause a > >> problem does not seem to be a good system. And sometimes > coding/programming > >> changes seem to fix one thing but bring up another problem - that > probably > >> means a bit more testing before a revision is released might be a good > idea. > >> > >> Tessa > >> > >> Tessa Keough > > > > > 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
