Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Location
    Pisgah, Charles County, Maryland
  1. I get this issue quite frequently. Re-indexing and optimizing don't help. Usually, I can clear it by opening the name tag for the person it defaulted to, making a change to the name and changing it back again and closing the window. I then navigate to the person it is confused with and do the same. In most cases that fixes things. I understand that logically that should not change anything, but logically this shouldn't be happening either so I roll with what works. On the few cases where that does not resolve the issue (most often it seems when the error has not occurred as a result of adding like-named children), I renumber each of the people getting mixed up. Whichever way I get it cleared up, I then re-index and optimize. I have never noticed a random person in the list of recently viewed people when this error occurs, I have noticed that it does not roll over to the person I am attempting to move to, but assumed that was because I didn't actually get to that person.
  2. 12Variable 'ROLE' is not found

    Sent - email with same title as this thread, thank you.
  3. I updated to 9.03 yesterday. One database is ok, another one gives this error when I start up. If I abort it then opens the Db. I have reindexed, run validation, optimized - all more than once - to no avail. Now what? 25-07-14, 08:52:51 12Variable 'ROLE' is not found. 6790 FIXROLE_E1 25-07-14, 08:52:55 12Variable 'LNCOUNTVAR' is not found. 6792 FIXROLE_E1 25-07-14, 08:52:57 12Variable 'ROLE' is not found. 6796 FIXROLE_E1
  4. Thanks for checking that. I feel better thinking it is still on the list rather than completely forgotten about.
  5. This is a link to the original thread. This was not fixed in Version 8 and is still happening in version 9. http://www.whollygenes.com/forums201/index.php?showtopic=13702&hl=
  6. Report Oddity

    Thanks, good to know I am not nuts
  7. Report Oddity

    No. I can get these same results in the same report for the same event. And it behaves the same way for every married female, not just one or two. It's odd isn't it. Are you able to replicate it?
  8. Report Oddity

    I know Prin1 Suffix (Selected) will do what I want, but that still leaves the options Prin1 Last, first (selected) and Prin1 first last (selected) behaving in different ways than expected. I would expect them to differ only in the order of the first and last names, not in which name they show and whether or not they include the suffix. I think I missed a part out of my original message. Matilda Gray married Thomas Dent becoming Matilda Dent (Gray). In my census tag I have selected her name as Matilda Dent. If I select Prin1 Last, first (selected) I get Dent, Matilda, (Gray) If I select Prin1 first last (selected) I get Matilda Gray My expectation would be that I would get Dent, Matilda or Matilda Dent Both selections are giving unexpected results.
  9. Report Oddity

    When a woman marries I enter her maiden name in the Suffix field as -(name) I like to run a List of Events report showing census households and I have noticed that when choosing columns if I choose "Prin1 Last, first (selected)" it gives me the name as selected in the tag (in this case showing the maiden name in parenthesis). But if I choose "Prin1 first last (selected)" the maiden name does not show up. Anyone else notice this? Is there a reason or is this a bug? I really would like to list these people as first last (selected)
  10. I had the same problem but I think I found a fix. I got the error message when I used the add husband button on the custom toolbar, but I went into the toolbar menu and recreated the add husband, wife, father, mother etc buttons and now they work.
  11. Crash when choosing sibling

    Same thing happening to me - it had gone away with the last upgrade, but seems to be back I'm not running Spy Sweeper. Any other fixes?