Jump to content


Photo

doubledating

date

  • Please log in to reply
8 replies to this topic

#1 fitz

fitz

    Advanced Member

  • Members
  • PipPipPip
  • 121 posts

Posted 11 January 2016 - 08:48 AM

I imported from TMG.  In the family I am working on, I have come across 4 instances where the date has been changed

 

Jan 1589/90 became 1590/91

1592/93 became 1593/4

Mar 1654/55 became 1655/56

Mar 1682/83 became 1683/84

 

I am assuming this is going to be this way every time there is doubledating.  Any way to fix this?  Thanks.



#2 kbens0n

kbens0n

    Advanced Member

  • Members
  • PipPipPip
  • 3444 posts

Posted 11 January 2016 - 10:21 AM

I just tried your examples inputs and got these results instead of what you state (all correct, by the way):

 

Jan 1589/90 remained Jan 1589/90 <--unchanged

1592/93 became 1592/3 <-- when third digit from left matches in both years, drop the second occurrence of that digit

Mar 1654/55 became Mar 1654/5 <-- when third digit from left matches in both years, drop the second occurrence of that d

Mar 1682/83 became Mar 1682/3 <-- when third digit from left matches in both years, drop the second occurrence of that d


---
--- "GENEALOGY, n. An account of one's descent from an ancestor who did not particularly care to trace his own." - Ambrose Bierce
--- "The trouble ain't what people don't know, it's what they know that ain't so." - Josh Billings
---Ô¿Ô---
K e V i N


#3 fitz

fitz

    Advanced Member

  • Members
  • PipPipPip
  • 121 posts

Posted 11 January 2016 - 10:32 AM

Yes when I input doubledating into RM it stays the same.  It is what was imported from TMG that is causing a problem.  Yes RM does use 1654/5 while TMG  uses 1654/55 my mistake on that.



#4 fitz

fitz

    Advanced Member

  • Members
  • PipPipPip
  • 121 posts

Posted 12 January 2016 - 01:39 PM

I just checked a couple of other families and the doubledating dates imported from TMG have been changed in RM such as

 

9 Jan 1615/16 in TMG became 9 Jan 1616/7 in RM



#5 Laura

Laura

    Advanced Member

  • Members
  • PipPipPip
  • 4276 posts

Posted 12 January 2016 - 11:14 PM

The 7.0.6.0 update fixed a problem of the TMG convertion offsetting double dates by one year.

#6 fitz

fitz

    Advanced Member

  • Members
  • PipPipPip
  • 121 posts

Posted 13 January 2016 - 04:36 AM

Thank you.  Will the update just fix the doubledating dates transferred from TMG and leave the doubledating dates I have since entered okay?



#7 kbens0n

kbens0n

    Advanced Member

  • Members
  • PipPipPip
  • 3444 posts

Posted 13 January 2016 - 08:29 AM

It won't change (correct) anything in your current database. It corrects how it handles the import into RootsMagic.


---
--- "GENEALOGY, n. An account of one's descent from an ancestor who did not particularly care to trace his own." - Ambrose Bierce
--- "The trouble ain't what people don't know, it's what they know that ain't so." - Josh Billings
---Ô¿Ô---
K e V i N


#8 Laura

Laura

    Advanced Member

  • Members
  • PipPipPip
  • 4276 posts

Posted 13 January 2016 - 10:15 AM

Yes, and if Fitz converted his TMG database before that update, his double dates would be off a year.

#9 fitz

fitz

    Advanced Member

  • Members
  • PipPipPip
  • 121 posts

Posted 13 January 2016 - 10:34 AM

Thank you.  Yes I converted before that update so I guess I am stuck with the wrong years.