After a comment on the mailing list for The Master Genealogist, I downloaded the trial version that supports TMG. But I am having problems: GenSmarts is indicating marriage places for people that aren't so.
For example, my wife's grandfather and his wife were both born and died in Ohio. I have no place for their marriage, only a date. But GenSmarts seems to think they were married in Butte, Montana. Which is where my grandparents were married.
And I haven't seen a suggestion that I didn't have on my own: check the various censuses and the land transactions.
On 2003-09-04 7:32pm GenSmarts replied...
GenSmarts will try and estimate places and dates where you don't have any specified if it can... in order to generate suggestions for you on where to look. If you look in the DATA CLEANUP, PLACE NAMES, you'll see a list of places GenSmarts estimated at the bottom of the list - they're prefixed with an F)
We need to do a better job of marking these so it's obvious when something comes from GenSmarts and when something comes from your file. For now, dates are prefixed with GSEST if GenSmarts is estimating them, and for places, the word PROBABLY should precede it.
We're planning on changing PROBABLY to GSEST. to be consistent. Also, the shorter forms of dates and places don't always carry the prefix, so that needs to be updated as well.
Sorry we didn't have any good suggestions for you. Check back from time to time and try out new versions as we post them - as we add new logic and new data and perhaps we'll have more for you in the future.
On 2003-09-04 8:19pm pheon added...
The word PROBABLY does not precede the incorrect place of these marriages. I don't understand why you make assumptions like that at all, given no data to support it whatsoever. That isn't helpful. It is just wrong.
I think GenSmarts is not ready for prine time. At least not with TMG databases.
On 2003-09-04 8:44pm GenSmarts replied...
Given your comment about not seeing the word probably, coupled with the fact there doesn't seem to be any basis for Butte, Montana... you're likely correct that this is simply a bug in the beta version. Though we can't now for sure without understanding a bit more about your data and your file.
If you'd like to help us make GenSmarts better, and/or for us to fix the problem, send an email to us at support@GenSmarts.com and we'll send you some questions and instructions that will give us the more detailed information we need to figure out what's going on. If you'd rather not, we'll understand.
On 2003-09-06 3:13pm GenSmarts replied...
FYI - problem did turn out to be an import bug, which should be corrected in the version currently posted.