[LegacyUG] Invalid date format

2017-06-29 Thread Barbara Lewis
This past week I've been running into some dates on my Legacy that look like this: 1869-05 and then showing on the "Task" screen, the Familysearch side: Problem: invalid date format Can someone tell me what that's all about? This is just since I download Legacy 9 Barb L, --- This email has

Re: [LegacyUG] Invalid date format

2017-06-29 Thread Terry L .
o:lewisro...@comcast.net> Sent: June 29, 2017 8:25 PM To: 'Legacy User Group'<mailto:legacyusergroup@legacyusers.com> Subject: [LegacyUG] Invalid date format This past week I've been running into some dates on my Legacy that look like this: 1869-05 and then showing on the &qu

Re: [LegacyUG] Invalid date format

2017-06-29 Thread Cathy Pinner
no idea why! Terry L. Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 *From: *Barbara Lewis <mailto:lewisro...@comcast.net> *Sent: *June 29, 2017 8:25 PM *To: *'Legacy User Group' <mailto:legacyusergroup@legacyusers.com> *Subject: *[L

Re: [LegacyUG] Invalid date format

2017-06-29 Thread Keith Drury Myers
Hi Barbara, It's a known bug in build 189. I reported it and has been told it has been fixed but the build with the fix has not been released yet! :-( This is giving me grief as I'm currently trying to sync my tree with family search. I keep on checking for a new build and am getting more a

Re: [LegacyUG] Invalid date format

2017-06-30 Thread Barbara Lewis
@legacyusers.com Subject: Re: [LegacyUG] Invalid date format Hi Barbara, It's a known bug in build 189. I reported it and has been told it has been fixed but the build with the fix has not been released yet! :-( This is giving me grief as I'm currently trying to sync my tree with family search.

Re: [LegacyUG] Invalid date format

2017-06-30 Thread Keith Drury Myers
ers.com] On Behalf Of Keith Drury Myers Sent: Friday, June 30, 2017 12:10 AM To: legacyusergroup@legacyusers.com Subject: Re: [LegacyUG] Invalid date format Hi Barbara, It's a known bug in build 189. I reported it and has been told it has been fixed but the build with the fix has not been relea