The programmer has responded to the problem report I entered. He has
decided that there is too much complication it trying to sort out what
part of a date is marked private so it can be treated as a good date.
Legacy allows many forms for entering dates and trying to sort out each
form when only part of the date is marked private is very complicated.
Also there is no way to "remember" which part of the date is private
once it has been marked as a good date that is private. Only dates that
are fully marked as private will be recognized as good dates.
Fortunately the reports do look for privacy markings within the bad date
since those are stored exactly as the user entered the date complete
with markings and will suppress the portion marked as private.

Legacy will therefore continue to pop up the unrecognized date screen if
you have date checking turned on in Options > Customize > Dates and have
entered a date that is only partly marked as private.

Brian
Customer Support
Millennia Corporation
[email protected]
http://www.LegacyFamilyTree.com

We are changing the world of genealogy!
When replying to this message, please include all previous correspondence.
Thanks.

On 20/04/2011 5:03 PM, Brian/Support wrote:
> A problem report has been entered in our system for this issue. As per
> Evert's email though the root problem is that dates using partial
> privacy markings are not recognized as dates.
>
> Brian
> Customer Support
> Millennia Corporation
> [email protected]
> http://www.LegacyFamilyTree.com


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://www.LegacyFamilyTree.com/Help.asp
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


Reply via email to