Announcement

Collapse
No announcement yet.

Strange codes appear

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Strange codes appear

    Some of the entries in my database have codes or numbers such as [[pt:1847]] or [[pt:2246]]. They often appear in a "Place" box but may appear elsewhere. What causes them, and how can I recover the original data that was in the affected boxes?

    #2
    Re: Strange codes appear

    Hi,

    The first thing you should do is ensure you have our latest update, 11.0.10, installed. You can download it here.

    Once that's installed, open your family file and rebuild caches using:

    File -> Rebuild Cache Files...

    If the [[pt:x]] entries persists after rebuilding caches, or are replaced with "** missing place" entries, you should send us your current family file along with a backup that contains the missing places. We should be able to restore the missing places from the backup.

    For details on how to send us your family file, please see this FAQ.

    HTH
    Mark Harrison
    Leister Productions, Inc.

    Comment


      #3
      Re: Strange codes appear

      Originally posted by ljirwin42 View Post
      Some of the entries in my database have codes or numbers such as [[pt:1847]] or [[pt:2246]]. They often appear in a "Place" box but may appear elsewhere. What causes them, and how can I recover the original data that was in the affected boxes?
      I saw the same thing when my system black-screen crashed while two Reunion files were open. Both also had index windows open at the time. The codes appeared in any location where Reunion's auto-fill function works.

      Obviously I've no idea what might have happened in your situation, but I had to replace the computer, a Mid-2010 MBP 15", to stop the crashes. That model became well-known for its faulty Nvidia GPU chip.
      -- Paul, Reitz immigrants in America

      Reunion 14 (build 241014)
      15" MBP_R mid-2015, macOS 12.7.6
      16" MBP M1 Pro, Sequoia 15.2

      Comment


        #4
        Re: Strange codes appear

        Hi Paul,

        The problem you most likely ran into is something we addressed in 11.0.9. Basically, if two files were opened at the same time and one (or both) required rebuilding of caches (which they would after a crash) there was a remote chance that you could end up with the [[pt:x]] codes.

        I can't say what caused your initial crash, but the problem with the [[pt:x]] entries was not a direct result of the hardware problems you ran into.

        That is, the problem was most likely not directly caused by hardware issues.
        Mark Harrison
        Leister Productions, Inc.

        Comment


          #5
          Re: Strange codes appear

          Originally posted by Mark View Post
          Hi Paul,
          I can't say what caused your initial crash, but the problem with the [[pt:x]] entries was not a direct result of the hardware problems you ran into...
          Mark, I appreciate the explanation. It should take care of ljirwin42's situation with Reunion.

          Crashes on the Mid-2010 MBP were occurring more frequently; the cause is well-known and a work-around exists, but it prevents use of an external monitor. So, not really a solution.

          The workaround is to use gfXCardStatus (v. 1.8.1) to lock out the Nvidia chip. The old MBP hasn't crashed since; so it might go to another family member.

          Some newer MBPs also have a video issue, for which Apple's repair program ends 12/31/2016. https://www.apple.com/support/macbookpro-videoissues/
          -- Paul, Reitz immigrants in America

          Reunion 14 (build 241014)
          15" MBP_R mid-2015, macOS 12.7.6
          16" MBP M1 Pro, Sequoia 15.2

          Comment


            #6
            Re: Strange codes appear

            Originally posted by ljirwin42 View Post
            Some of the entries in my database have codes or numbers such as [[pt:1847]] or [[pt:2246]]. They often appear in a "Place" box but may appear elsewhere. What causes them, and how can I recover the original data that was in the affected boxes?
            Did you at one time import a gedcom into your database?

            I mention this as I was helping a friend some time ago and we saw something similar in her database. When we looked further we determined the codes had appeared when the gedcom she was importing was not converting some of the data. I think how we ended up solving it was to see those same codes showing when we looked at her preferences - I believe it was under "field preferences". It was a long time ago so may have been in a different preference.
            Laura Turnbull

            Comment

            Working...
            X