I know this is pretty obscure, but I saw several people saying they were having issues with TreeShare not finding hints. I wasn’t able to find a case in my database where hints were showing on Ancestry but not in WebHints. Until Today.
This workaround isn’t for the faint of heart, but if you know the id of the person in question and have access to a SQLite Manager you can do:
UPDATE AncestryTable SET Modified = 1 WHERE LinkType = 0 and rmId = (id of person in question)
No, this solution likely isn’t endorsed by RootsMagic (so don’t shame me Renee) but it worked like a champ for me.
I don’t want to make too much of this - especially if I’m wrong - but I wonder how that modified flag gets set in normal use? I wonder if it gets set automatically when you connect up to Ancestry via TreeShare, even if you just let things sit there. I virtually never actually connect up to TreeShare anymore. And I virtually never get hints from Ancestry anymore. I wonder if the two are related.
At this point I was just messing around trying to figure out a way around the problem. Based on my previous TreeShare adventures I knew it was either the AncestryTable or the AT_ file. Not knowing exactly what “Reset TreeShare” does (Please Renee, can dev explain it??) and my unwillingness to being forced to resync 40,000+ entries I got adventurous and decided maybe I’d delete the rows in AncestryTable, but then thought maybe I’d try something less drastic and Valla! it worked.
I’d like to document the table fields better, but for today I had more pressing business and thought I’d just post up what I found.
“Reset TreeShare” will delete the .DT8 file. It will have to rebuild the index the next time TreeShare is opened. So TreeShare will be slower opening while it does that. It’s a housekeeping tool.