Jump to content


MikeZ

Member Since 28 May 2004
Offline Last Active Jun 21 2018 09:43 AM
-----

Posts I've Made

In Topic: "Collecting Changes from Ancestry" marks everything changed, etc.

11 July 2017 - 05:10 PM

 

Confirming that is on the development list.

Thank you!!


In Topic: "Collecting Changes from Ancestry" marks everything changed, etc.

11 July 2017 - 10:02 AM

After spending the past 30 minutes clicking through a list of hundreds (I estimated 80, boy was I wrong!) of "changed" people I'll take back my "manageable, but puzzling" comment.   We really need some type of global list selection (via the CTRL/Shift key & RMB) in the Treeshare window to allow a user the option of quickly clearing their "changed" list.


In Topic: "Collecting Changes from Ancestry" marks everything changed, etc.

11 July 2017 - 09:44 AM

On the RM side we do know of things that will cause large numbers of people to be on the change list. If you edit the Master Source or the Place List (for now) everyone associated with them will be on the change list. I can't think of anything else right now that could put a large number of people on the changed list. 

This may be why I'm seeing considerably more people flagged as "change" than I expect.  I did make changes to a few sources, and merged a few places...


In Topic: "Collecting Changes from Ancestry" marks everything changed, etc.

11 July 2017 - 09:41 AM

 

When your typing in the TreeShare index you start with surname, then comma, then given name. Its the comma after the surname that some database will not go any further in the incremental search. As soon as you add the comma it will start over in the index with the next letter you type. Not all databases are behaving this way.

Thank you for this.  Although every person in my entire DB was flagged once as "changed", I do not recall ever typing in any names or a comma.  After the first instance, it has not happened again.  However, recently I am noticing some people flagged as "changed" that I do not recall changing any related information, and  when I compare the RM vs. Ancestry sides the only item that is different is some RM facts have a source icon shown where the Ancestry facts do not - but I the fact source are not new...

 

After adding 10 people to my RM DB yesterday, I clicked on the Treeshare icon and was shown a list of perhaps 80 people flagged as "changed" - manageable, but puzzling...


In Topic: "Collecting Changes from Ancestry" marks everything changed, etc.

10 July 2017 - 08:35 PM

I got a taste of the frustration you must feel over this matter, but I was fortunate in that I could restore my DB leaving only 3 people to add.  With everyone in a changed status it negates the utility of that feature.

 

And I still would like an answer to my earlier question, "where in a person's name does the comma have to be to trigger this?"  I believe knowing specifically what causes this issue is important - a couple of examples would be helpful...