Pete, Support is really the place to sort out this persistent type of problem.
But a thought - how are you creating the new file? Are you importing lists from another file or is it really a clean new file that is immediately crashing? If you are importing lists, one of them may be the problem. Your computer date setting shouldn't be a problem. Mine is also set to DD-MM-YYYY - also the Australian standard. I use Custom Events and lots of my own Sentence Definitions, so I don't think that in itself is the issue either. Speedy entry can cause a freeze or crash of Legacy - but I haven't seen the 3021 error for a long time. Cathy Forefathers Research wrote: > > This has happened 12 times to me this afternoon, on a file I created > this afternoon. > > I have run file maintenance 3 times. > > I am close to ditching Legacy, despite the fact it has the best source > writing system I know. Can anyone suggest anything? > > Pete > > On 14 August 2015 at 10:09, Forefathers Research > <[email protected] <mailto:[email protected]>> wrote: > > This has happened to me three times this morning already. > > As I've mentioned before, the 3021 crash always occurs when I have > just entered a date for a custom event. > > One thought that just came to mind is whether the fact that I have > UK/European date format DD MM YYYY selected could be relevant? > Could that explain why it affects me but not the majority of other > users? > > 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 > Technical 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 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
