|
|
Customers GenoPro version: 2.0.1.4
Last Login: Tuesday, September 27, 2022
Posts: 64,
Visits: 5,071
|
The export to gedcom via report writer produces a HEAD record with an erroneous date. A gedcom generated on 22 Jan 2008 has a header date of 2 Jan 2008, three gedcoms generated on 5 Jan 2008 have header dates of 6 Jan 2008 and two on 6 Jan 2008 have a date of 0 Jan 2008 which is clearly nonsense. It does seem to be consistent from day to day but I still can't see the pattern other than that the dd part always seems to be a single digit.
BobC
|
|
|
Administrators Customers Important Contributors FamilyTrees.GenoPro.com GenoPro version: 3.1.0.1
Last Login: 1 hour ago
Posts: 3,436,
Visits: 26,607
|
Thanks for reporting this BobC. I have mistakenly used the JScript function getDay() that returns the day of the week (0-6) and not the day of the month. I should have used getDate() instead. You can correct this for now in a custom skin. Change line 37 of gedcom.js to:
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Edited: Friday, January 25, 2008 by
Ron
|
|
|
Customers GenoPro version: 2.0.1.4
Last Login: Tuesday, September 27, 2022
Posts: 64,
Visits: 5,071
|
Thanks for the prompt reply Ron. It was an annoyance more than anything else -I just manually edited the gedcom, but if you don't know it's broken you can't fix it.
BobC
|
|
|
Customers GenoPro version: 2.0.1.4
Last Login: Tuesday, September 27, 2022
Posts: 64,
Visits: 5,071
|
Ron,
A minor point - I made the change and it works fine, the only thing is the code is on Line 163 not Line 37 that you mentioned. It's so far adrift I wonder if I've got an odd gedcom.js ; I've never edited it before. It's version 1.2 date last updated: 5th December 2006
BobC
|
|
|
Customers Important Contributors GenoPro version: 3.1.0.1
Last Login: 10 hours ago
Posts: 443,
Visits: 7,712
|
The latest version is 2.0.0.3 ( included in GenoPro 2.0.1.4), but oddly internally it is dated as last updated 9th February 2006, which is earlier than your version . The coding begins at line 37, but the phrase in question is now at line 184.
|