Loading ...
Sorry, an error occurred while loading the content.

1374RE: [AQ_NFS] NFS updates to AQ

Expand Messages
  • sm99923
    Jul 19, 2013
    • 0 Attachment
      A case of "humble pie" is called for . . . I had not updated to build 13 . .
      . which removed the problems - horrible taste 'umble pie!


      From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On Behalf Of
      Sent: 19 July 2013 12:40
      To: AQ_NFS@yahoogroups.com
      Cc: gfindlay@...
      Subject: RE: [AQ_NFS] NFS updates to AQ

      A further test to my original note shows:

      In attempting to update from FT to AQ - where there is no AQ entry for the
      event (in this case a Birth) - on the FT side - after selecting the event to
      download to AQ - the FT side has not activated the drop-down selection for
      the "sync options" to take on the AQ side for the selected birth entry -
      the "synch options" do appear for every other non-selected item on the FT

      So without any confirmation of what synch action might be taken on the AQ
      side - completing the operation with the Save button results in no
      update/transfer to the AQ data.


      From: AQ_NFS@yahoogroups.com <mailto:AQ_NFS%40yahoogroups.com>
      [mailto:AQ_NFS@yahoogroups.com <mailto:AQ_NFS%40yahoogroups.com> ] On Behalf
      stew999@... <mailto:stew999%40gmail.com>
      Sent: 19 July 2013 12:08
      To: AQ_NFS@yahoogroups.com <mailto:AQ_NFS%40yahoogroups.com>
      Cc: gfindlay@... <mailto:gfindlay%40ancquest.com>
      Subject: [AQ_NFS] NFS updates to AQ

      I have in the past carried out updates between AQ and nFS/FT in both
      directions - successfully.

      I have just tried to change an AQ Christening date and place with the FT
      date and place (date was the same but the place was slightly different) -
      taking care to select on the FT side the "Replace local event/fact" option.

      Completing the action with "Save" results in no update of the AQ record.

      Have tried several times with the same result - have not yet tried with any
      other event requiring a similar change from FT to AQ (not many differing


      From: AQ_NFS@yahoogroups.com <mailto:AQ_NFS%40yahoogroups.com>
      [mailto:AQ_NFS@yahoogroups.com <mailto:AQ_NFS%40yahoogroups.com>
      <mailto:AQ_NFS%40yahoogroups.com> ] On Behalf
      William Knight
      Sent: 13 July 2013 12:40
      To: AQ_NFS@yahoogroups.com <mailto:AQ_NFS%40yahoogroups.com>
      Subject: Re: [AQ_NFS] New Build 13 of AQ 14

      Been doing merges since installing newest update and working flawlessly,
      even that nuisance error is gone.
      Bill Knight

      From: Gaylon Findlay <gfindlay@... <mailto:gfindlay%40ancquest.com>
      To: AQ NFS <aq_nfs@yahoogroups.com <mailto:aq_nfs%40yahoogroups.com>
      <mailto:aq_nfs%40yahoogroups.com> >
      Sent: Friday, July 12, 2013 9:12 PM
      Subject: [AQ_NFS] New Build 13 of AQ 14


      We have just released build 13 of AQ 14.

      It addresses issues that we have heard about from several users.

      To upgrade, you can either bring up your "Newsline" window from AQ's Help
      menu, and click on the link to update, or you can go to AQ's Internet menu,
      and select "Check for Latest AQ Release." Either way will get the same

      Below is a plain-text version of the list of enhancements and fixes.


      Changes in Build 13 (07/12/2013)

      General Bug Fixes

      * AQ Seems to Hang: Occasionally, one of the screens would come up out of
      view, making it appear that AQ had locked up. Fixed.

      Enhancements to FamilySearch Features

      * Merging Family Tree Records: Prior to checking to see if FamilySearch
      considered the merge of two Family Tree records to be viable, AQ would take
      the time to load all the information needed to complete the merge. For some
      records this could take considerable time. AQ now checks the viabilty first,
      and if the merge will not be allowed, alerts the user and does not load all
      of the information.

      * Family Tree PID Change: If FamilySearch had changed the PID of a record to
      which you had linked one of your records, when AQ next attempted to work
      with that record, it would display a message to let you know the new PID.
      This became annoying when you were running a long process like checking for
      changes or updating LDS ordinances. In these two processes -- Check for
      Changes and Update Ordinances, AQ no longer provides this message.

      Bug Fixes to FamilySearch Features

      * Crash on Program Exit: On 7/10/2013, FamilySearch disabled AQ's ability to
      update the older "New FamilySearch" database. One of the changes made by
      FamilySearch in that process caused AQ to crash when you exited AQ, if you
      had logged into FamilySearch during your session with AQ. Fixed.

      * Merging Records on Family Tree: If you started the screen to initially
      match one of your records with the corresponding record of Family Tree, and
      you found several duplicates, AQ would merge the first set of duplicates
      properly. But if you attempted to merge a second set of duplicates before
      exiting that screen, AQ would give unwarranted error messages or crash.

      * General Updates: Occasionally, if FamilySearch was a bit slow when you
      tried to update information to Family Tree, you might get an error message,
      even though the update was successful. Fixed.

      * Family Sync: If the PIDs of relatives had changed in Family Tree, the new
      IDs were not always updated yet to your database, so family members in your
      file sometimes appeared to be linked to the wrong records in Family Tree.
      This often caused you to try to correct this, when no correction was needed.
      This usually ended up giving unwarranted error messages when attempting to
      adjust family links. Fixed.

      * Family Sync: If you sent data to Family Tree from the Review and
      Selectively Sync Individual screen while going into the Family Sync screen
      for either Parents/Siblings or Spouses/Children, you would often not see the
      family from Family Tree. Fixed.

      [Non-text portions of this message have been removed]


      Yahoo! Groups Links

      [Non-text portions of this message have been removed]

      [Non-text portions of this message have been removed]

      [Non-text portions of this message have been removed]

      [Non-text portions of this message have been removed]
    • Show all 4 messages in this topic