Sorry it took so long to get back to you.In answer to your question, no, a new file from scratch does not crash Generations...so far...so it probably is a corrupt .UDS file.The versions before 8.5.1 crashed numerous times for me, especially when entering data in the notes field and I suspect that when it was re-building the index each time on restart, all my problems began.
This week, I weeded out lots of zombie records (1. click on a name in the index and nothing happens, 2. click on a name in the index and it goes to a blank record, 3. blank record showing on index & is incorrectly linked to wrong family, etc.).After performing this file maintenance, I found that if I entered new people into the database, they're being assigned an ID# that's already in use instead of one of the ID#'s that's unassigned.
For instance, I entered the following two families using Add Unrelated Person:
*Jane Doe married to spouse #1 Joe Somebody, and spouse #2 James Whomever
*Bob Red married to spouse #1 Cindy White
Save & Exit from Generations, then go back into the file a few hours later and I find this:
Bob Red married to Joe Somebody or Cindy White married to Jane Doe.James Whomever linked as a child of Jane Doe & Joe Somebody, etc.Sometimes you can look at a family card and nothing appears amiss...until you print out a family group sheet and see that the SOMEBODY family has all the WHOMEVER children linked to it or something to that effect.So, the corruption has to be in how Generations is handling ID# assignments.I can even delete all these people and re-enter them and the same thing happens again.I'm beginning to think I may have to run Generations under Windows Safe Mode because I can't find any program or device in msconfig that's conflicting with it. It's a mystery to me.Maybe you know a work-around?
Also wanted to ask you about the v.8.5a patch...I didn't receive a copy of that patch from you when I ordered unless it was already incorporated on the CD-ROM I received.If not on the CD, is it something you can e-mail?