Hmmm...interesting. I just tested it out myself and could not replicate the anomaly. I was beginning to think that 9/30/2009 was some kind of magical date that caused all sorts of programming problems. I should think that the Legacy program is actually using a call to the Windows OS for current date so the only thing I can think of is that somehow your system date was reset and you never noticed it.
Brian in CA -----Original Message----- I just clicked on the "Today's Date" button when adding a recorded date on my source detail, and the date came up as October 30, 2009 instead of September 30, 2009. It was working correctly up until yesterday, and I updated to the latest build (7.0.0.109) earlier this morning. <>< <>< <>< <>< <>< <>< <>< Peter W. Wielhouwer, Ph.D. Mattawan, Michigan, USA pwielhou...@comcast.net Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
