FTM 2019 incoming

[Helen7]

Tim/Helen7
Two extracts of descendant charts attached - one from FTM the other from FH
Phil

Oh I see. Yes, I've been able to reproduce this effect in my own family tree on FTM. It's very odd how the children are attached only to the parent on the right (whether mother or father). I've never noticed this in FTM before, probably because I've only really used the pedigree and relationship charts rather than the descendant charts.

 

[At home in NZ]

the ability to switch between Trees

Surely we have that ability in FTM 2017? I have 5 trees that I sync with Ancestry and often switch from one tree to another in FTM 2017. What is so different in this new version?

 

[Bob Spiers]

Surely we have that ability in FTM 2017? I have 5 trees that I sync with Ancestry and often switch from one tree to another in FTM 2017. What is so different in this new version?

I was commenting on FTM as a package, not one version against another and of course some things will remain the same regardless of the version used. As a pragmatist I tend to accept that new innovations improve on old, and in the main they do. But tempered with that is of course how much something costs, and whether new features are attractive enough to warrant its purchase.

On a broader spectrum think of Windows. Many people refused to upgrade from XP (despite security risks) and many, many more face the same decision with Windows 7 when it ceases to be supported by Microsoft next year. In the latter case they could all have upgraded without charge, but for their own reasons, some decided it was not for them. As they read of the shenanigans surrounding W10 downloads, they are likely happy they chose not to upgrade. Personally I think it folly, but that is just my opinion.

So with FTM as the song says... "IF YOU'RE HAPPY & YOU KNOW IT, CLAP YOUR HANDS" I was happy to upgrade (despite the rampant commercialism of Mackiev) and hopefully will remain happy using the new version.

Each to their own!

 

[At home in NZ]

Each to their own!

Agree.
You mention new innovations have you ever heard of an old innovation?
I believe the word innovation is a stand alone. It means new.
The rapid race to change the meaning of our language is making nonsense of it.
I digress and find myself guilty of getting 'off topic'.

 

[jorghes]

I got my link finally last night.

It meant (after download) that I could sync my tree after weeks of attempted sync + program randomly shutting down mid sync. Unfortunately it then duplicated everything again, and I have to keep working on removing duplicate people!

 

[canadianbeth]

I am still seeing "orange" every time I open the program. Is anyone else having this problem? I received the e-mail on the 4th but have been hesitant to download it.

 

[At home in NZ]

I am still seeing "orange" every time I open the program. Is anyone else having this problem?

I am using FTM 2017 and seeing Orange and I am not letting it stop me from syncing. Provided you do a compact file with back up and compact again until it shows 0.00%
Then run the sync making sure you download the changes into PDF and file the PDF with your FTM files all should be well.
It works for me.

 

[Helen7]

I am using FTM 2017 and seeing Orange and I am not letting it stop me from syncing.

I have upgraded to FTM 2019 and I have also been seeing 'orange' for the last 10 days, but I successfully synced yesterday with no problems (after making sure I had a full backup just in case!)

 

[jorghes]

I think the Orange simply states "don't sync again if it fails" - but yes, it has been orange for weeks now, but mine has been syncing with FTM 2019 quite well every time I've tried, although attempting to sync with FTM 2017 was crashing the program leading up to my updating.

 

[canadianbeth]

That is my concern. I still have 2017 because the instructions for downloading 2019 say to sync to Ancestry first. I know it says do not sync again if it fails but I am concerned that it will fail. I have enough problems with this (new) computer without that happening as well.

ETA: I tried syncing and got a message saying there was a problem, with a form to fill out stating the problem. I just cancelled and will not try again until I see green.

 

[jorghes]

That is my concern. I still have 2017 because the instructions for downloading 2019 say to sync to Ancestry first. I know it says do not sync again if it fails but I am concerned that it will fail. I have enough problems with this (new) computer without that happening as well.

ETA: I tried syncing and got a message saying there was a problem, with a form to fill out stating the problem. I just cancelled and will not try again until I see green.

Is it already on Ancestry your tree?

I didn't bother attempting to sync before I updated, because I do the majority of my work on my tree on Ancestry, and thus what was online was more up to date than what was on my laptop. Thus when I updated, I could sync all the adjustments easily.

 

[canadianbeth]

My tree is on Ancestry, but I have updates on FTM that needed to be sync'd to Ancestry, as the e-mail suggested. So you did not bother? I just wish they would fix the "orange"; does anyone know why it has been that way for so long?

 

[jorghes]

My tree is on Ancestry, but I have updates on FTM that needed to be sync'd to Ancestry, as the e-mail suggested. So you did not bother? I just wish they would fix the "orange"; does anyone know why it has been that way for so long?

No, not before I updated - I couldn't anyway, every time I tried syncing FTM 2017 to Ancestry it failed and the program crashed.

It downloaded, upgraded the file and then synced properly for the first time in weeks.

Probably best to back up the FTM file and then try it without syncing first.

 

[Bob Spiers]

I keep both my Tribal Pages and Ancestry in line -in other words an update on one is then done (manually I might add) on the other. So that means Ancestry will always have the latest update, and so when FTM is synced with same, that too will be updated. In short my sync's are always one way, FTM being updated to align with Ancestry.

So returning to candadianbeth's problem where she updates on FTM and wishes to sync to update Ancestry, I understand the nuisance of wanting to get Ancestry in line with FTM and not being able to because syncing whilst orange has failed and she must wait for the green light, so to speak.

Surely the procedure with 2017 is (as has been pointed out already) is to do a backup and compact until you get the 0% result. Then I'm afraid you have little option but to wait for the syncing process to revert to green. Once Ancestry aligns with FTM 2017, then you are all set to use the 2019 update and sync that with Ancestry.

 

[canadianbeth]

I am using FTM 2017 and seeing Orange and I am not letting it stop me from syncing. Provided you do a compact file with back up and compact again until it shows 0.00%
Then run the sync making sure you download the changes into PDF and file the PDF with your FTM files all should be well.

Surely the procedure with 2017 is (as has been pointed out already) is to do a backup and compact until you get the 0% result.

I do not understand the compact until you get 0%. I just click on file and then backup and ok. Is there something else I should be doing?

And downloading changes into pdf?

 

[PhilGee]

"Compact" is in the "tools" drop-down list. It cleans up the file which makes it smaller. There are options to backup and perform an analysis; the latter recreates the indexes etc. improving access speeds.
Phil

 

[Bob Spiers]

I do not understand the compact until you get 0%. I just click on file and then backup and ok. Is there something else I should be doing?

Compacting a file is not the same as Backup. As PhilGee says you go to Tools and find the Compact tab. Click on this. When it completes check it reports 0.00% (think of that as an 'all clear'). If it shows any higher percentage (0.05% or higher) you need to compact again until you achieve 0.00%.

(Remember to do both Backup and Compact though strictly speaking Compact need not be done every time you backup, but it is a good discipline to do so perhaps weekly, or if you receive a message to Compact your file. That said it is advisable to do both whilst you await the 'green light' so to speak)

And downloading changes into pdf?

Yes I'm afraid I'm as much in the dark on the need to save to pdf after syncing as you. I just Sync and await a Sync completed message. Perhaps someone else can explain why anyone should save to pdf?

 

[At home in NZ]

I'm as much in the dark on the need to save to pdf after syncing as you

Everything I said is what I learnt from reading the instructions given by McKiev.
To explain the creation of pdf:
While the sync is progressing it brings up this screen:

click on the View/Print Details button which will allow you to see all the changes you have made, from there you can create a pdf.
File the pdf so you can go back to it if you find syncing has messed your tree up and you need to know what you did.

 

[jorghes]

Everything I said is what I learnt from reading the instructions given by McKiev.
To explain the creation of pdf:
While the sync is progressing it brings up this screen:
View attachment 1636
click on the View/Print Details button which will allow you to see all the changes you have made, from there you can create a pdf.
File the pdf so you can go back to it if you find syncing has messed your tree up and you need to know what you did.

considering FTM2019 says it saves 1000 past changes (or whatever it was) you would only need the PDF when you were syncing changes from Ancestry, right?

 

[At home in NZ]

considering FTM2019 says it saves 1000 past changes (or whatever it was) you would only need the PDF when you were syncing changes from Ancestry, right?

I was actually talking about FTM2017 and addressing the problems people were having with syncing FTM2017 before changing to FTM2019.
I always work in Ancestry and sync into FTM, working in both and syncing was causing problems for me.
I had an awful 'failure' which meant I had to unload and re-load my tree I have followed McKiev's instructions for syncing and never had a problem since.