When entering dates for sources Legacy does not always use the same date validation and reformatting that is applied to dates in other places. As a general rule the date validation and format MAY be applied the first time you enter a date but when the date has been stored it becomes a simple string of characters insofar as the database is concerned. If you later amend a date NO validation is applied to the change and the user becomes responsible for entering exactly what they want.
Especially in Sourcewriter sources the date validation/formatting routines were also not implemented even on the initial entry so for most Sourcewriter dates you have to enter your own dates the way you want them to appear. Brian Customer Support Millennia Corporation [email protected] http://www.LegacyFamilyTree.com On 14/11/2012 10:51, Pat Hickin wrote: > Can someone tell me why it is that when I am entering source data and have > a field labeled "Date" or "Date Recorded" and I enter the date as > MM/DD/YYYY Legacy converts the date to, say, "07 Nov 2012" and at other > times leaves it as "11/7/2012." Since the latter could be misconstrued as > "11 Jul 2012" it would seem desirable for Legacy to make the conversion so > that I could correct it if necessary. > > Does anyone know the reason why certain date fields are NOT converted > (although most of them are)?? > > Thanks, > Pat -- 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
