OK, I know I'm probably anal but this bug--er, feature is driving me crazy! Maybe someone else has a better way to do this.
Here's the problem: I select event number 1 to add an event--let's say I'm adding a birth event--and I enter the date in the freeform date field as Sep 6, 1888. So far, so good. Now I want to create their spouse's record and that puts it into event number 2 as their marriage event. But, unfortunately, I don't know their marriage date. So I leave the free form date blank. Now I select event number 3 to add their death information. I know where they died but not the date of death. OK, I'm done with the record. So I press F9 to save the record.
Now all of a sudden the marriage and death events are before the birth event! Why can't event number 1 stay event number 1 and event number 2 stay event number 2? Or, why isn't the application smart enough to know that a birth event comes before a marriage event and both come before a death event?
I tried asking technical support and their work around was to put a "fake" date in the sort date field, i.e., birth free form date Sep 6, 1888; wedding sort date 1908; death sort date 1958. But I HATE the idea of inputting "fake" dates in the sort date field!
Has anyone else figured out a way to get event number 1 to stay event number 1, event number 2 to stay event number 2, etc.? Given my programming experience and my data entry experience, entering "fake" dates really goes against the grain!!
|Home | Help | About Us | Site Index | Jobs | PRIVACY | Affiliate|
|© 2007 The Generations Network|