Old Family Portrait
 

Latest Release Information for AQ 14

The most current release of Ancestral Quest 14 is Build 34. All changes made to AQ 14 since its initial release are listed below.

There is a newer major release of Ancestral Quest. It is version 16. The current build is 12. For a specially priced upgrade fee, you can upgrade to this new version of the software.

Changes in Build 34 (9/7/2016)

Enhancements to General Features

  • WorldConnect Tree Links on Pedigree View: Ancestry.com has had trouble delivering proper information on the number of Trees in the RootsWeb (WorldConnect) project for several weeks. This build will recognize when Ancestry.com is having trouble, and provide you with a link to search for trees on RootsWeb. This search has been improved to give you better results, by searching not only on name, but also on birth year.
  • Scrapbook Links: When a scrapbook link was broken (most usually because you moved a photo to a new folder), AQ would allow you to search for the new location. One of the screens that is shown now includes the name of the file you are looking for, rather than have you rely on memory.
  • Check/Repair: A couple of improvements were made to Check/Fix to find a couple of unusual data issues.

Bug Fixes to General Features

  • GEDCOM Import: When importing a GEDCOM file which included images for sources, in some cases the images were not properly attached to the correct source. Fixed.
  • Translations: Some status screens were not showing the translation, rather always showed in English. Fixed.

Enhancements to FamilySearch Features

  • Reserving Ordinances: If you were using the "Create Batch" screen of AQ's Ordinance Reservation and Tracking System (an LDS specific feature), such that you were opening and closing this screen often, AQ now reloads the screen much more quickly.

Bug Fixes to FamilySearch Features

  • Error Code Changes: Over the last few months, FamilySearch has changed some of the codes they send to AQ, causing AQ to give less helpful messages. This build handles these altered codes:
    • Several users have received lots of 403 errors, when FamilySearch changed the IDs of records of living people. In these cases, AQ will now report the IDs as no longer valid, and make it easier to re-link the records.
    • When AQ updated marriage data on FamilySearch, a changed code caused AQ to report that the update was unsuccessful, when in fact, the change had been made. AQ no longer improperly reports a problem in this case.
    • When users would run the feature to Check for Changes on FSFT, if certain new error codes were encountered, it stopped the process. Now the process will continue, and simply skip the record with the new codes.
  • Syncing Sources: An improvement was made to the way sources are attached to various events for individuals when syncing sources with FSFT.
  • Other: A few other minor bugs were fixed in syncing.

Changes in Build 33 (1/12/2016)

Enhancements to General Features
  • GEDCOM Import: When the import process finds a problem with data in the GEDCOM file, it now provides additional detail to help understand and locate the problem.
  • GEDCOM Import: When importing from FTM, additional improvements were made, including:
    • In the rare case that the user had attached multiple images to a source, AQ was retaining the last image, but now retains the first, and reports the others in the listing file.
    • While media items attached to various marriage events were being attached to the scrapbook of the husband or wife, media items directly attached to the marriage record were not being imported -- these are now attached to the scrapbook of the husband or wife.
    • If the user was LDS and had attempted to add temple ordinance information in FTM, improvements were made to recognize more ways a user might have attempted to record temple names, and convert these to standard temple names/codes.
    • Sometimes FTM exported part of an individual's contact address in a way that was missed by earlier versions of AQ. For these cases, AQ will now import this part of the address.
  • Date Formats: You can now choose to display dates with the full month spelled out. For example, in addition to showing a date as "12 Jan 1816", "1/12/1816", or various other abbreviated ways, you can now choose to show it as "12 January 1816". Choose this in the Formats tab of Preferences.
Bug Fixes to General Features
  • Web Page Creation: In one situation, when AQ created a link to view a source image on the page, it used a '\' (backslash) as part of the path (as used in Windows) rather than a '/' (forward slash) (as used for web links). Some browsers adjusted for this, but others did not. When they didn't, the links to these images didn't work. Fixed.
  • GEDCOM import from Ancestry.com The 'type' (ie, Photo, Document, Other) for some media items was not set during import, requiring the user to manually select a type. Fixed. (Note that media links from Ancestry.com are typically links to web pages, rather than to files on your computer. While Ancestry.com often provided links that would work properly outside of Ancestry.com, many of these links seem to be of a nature than can only be used from within Ancestry.com, so may not properly show a page when used from AQ or directly entered into a browser.)

Recommendation: If you have just imported an FTM GEDCOM file into AQ within the last few days prior to the release date of this build (1/12/2016), and you felt that the import missed some items, you might update to build 33 of AQ 14, then try the import again to a new Database and see if more data is imported. (Most users will not have these situations.)

Changes in Build 32 (12/21/2015)

Bug Fixes to General Features
  • GEDCOM Import: When importing GEDCOM files from Family Tree Maker, all of the media files were imported in earlier versions, but the selected portrait photo of FTM was not set as the default photo in AQ. Fixed.
  • GEDCOM Import: When importing GEDCOM files from Family Tree Maker, if a media item was linked to multiple people in FTM, it was linked only to the first person in AQ. Such items are now linked to all person records in AQ as they were in FTM.

Recommendation: If you have just imported an FTM GEDCOM file into AQ within the last few days prior to the release date of this build (12/21/2015), and that file contains a significant number of pictures, you should update to this build of AQ and reimport your file. If you only have a handful of persons with media items, you could manually select the default photo of each person without needing to reimport your file.

If you are not importing GEDCOM files into AQ from FTM, there is no need to update to this build, unless you have not already updated to build 31. If you have a version of AQ older than version 14 build 31, you will want to update now.

Changes in Build 31 (12/17/2015)

Enhancements to General Features
  • GEDCOM Import: Improvements were made to handling the unique way Family Tree Maker (FTM) created GEDCOM files, so that FTM users will be able to confidently import their data into AQ from FTM and Ancestry.com.
Enhancements to FamilySearch Features
  • Standardized Place Names: Improvements were made to the new ability to select standardized place names when uploading data to FSFT.

Changes in Build 29 (11/05/2015) and Build 30 (11/12/2015)

Note: Build 29 was released on 11/5/2015, with the primary purpose of providing those who use the features which interface with FamilySearch Family Tree (FSFT) the ability to select Standardized places, when sending place information from their own file to FSFT. After a few users had started using this new feature, a bug was discovered that we decided to fix before additional users would download build 29. So most users never downloaded build 29. The reported bugs were fixed in build 30, which is now available to all users.

Enhancements to FamilySearch Features
  • Standardized Place Names: When selecting an event to upload to FSFT, you will now be asked to select a standardized place name. You will also be able to see the standardized place name selected by you or others when you examine the details of an event on FSFT.

    NOTE: The purpose of build 29/30 is to meet a change in certification requirements of FamilySearch, in that FS now requires selection of a standard place name.

Changes in Build 28 (9/29/2015)

Enhancements to General Features
  • GEDCOM: Two of the new features of AQ 14 are Color Coding and Tags. Until now, if you had set tags for individuals, or had used color coding to highlight certain individuals, GEDCOM would not retain these items. Now it will retain tags and color codings that are not likely to interfere with the destination file.
Enhancements to FamilySearch Features
  • Syncing Sources: When syncing sources between your personal file and the public FamilySearch Family Tree, AQ now records the linkage between these sources, thus improving the likelihood that AQ will not create duplicate sources on either your personal file or in FSFT. (You can now also optionally see the FSFT source ID.)
Bug Fixes to FamilySearch Features
  • Logging Out of FSFT: Around August 10, 2015, FamilySearch broke their API which allowed AQ to logout of FSFT. Because AQ always tried to logout if you had logged in to FSFT, most users experienced an error message every time they exited AQ after 8/10/15, if they had worked with FSFT during their AQ session. AQ no longer attempts to logout when you close AQ -- understanding that by simply ending the session, a logout is presumed. So this problem is fixed.

Changes in Build 27 (7/23/2015)

Enhancements to General Features
  • Advanced Filtering/Focus: Improved the filter for locating individuals with sources.
Bug Fixes to General Features
  • Publish a Family Book: If you did not select any of the intro pages such as the Cover Page, Title Page, etc, so that the Table of Contents was the first page, the TOC sometimes would not display properly. Fixed.
  • Publish a Family Book: If you included a Cascading Pedigree Chart as a chapter in the book and selected the Index, the names of ancestors for that chart would all be listed as showing on the first page of the cascading set of charts. Fixed.
Enhancements to FamilySearch Features
  • Reading LDS Ordinances: For some records in FSFT, the FamilySearch system is not able to provide the LDS Ordinances. For such records, it tries for several minutes, and then gives up. AQ now has an enhanced ability to mark such records so that it won't attempt to read LDS Ordinances for those records for a few weeks, thus speeding up AQ's ability to display best data to the user.
  • Importing Family Lines: Occasionally, FSFT would get lost and not provide some records that it listed as available. In these cases, AQ would abort the import. Improvements were made so that AQ will now simply skip these cases and continue with the import.
Bug Fixes to FamilySearch Features
  • Reading LDS Ordinances: Around 7/20/2015, FamilySearch made some changes to the way it handled LDS ordinances that could be reserved when the deceased person was less than 110 years old, as it now enforces this rule more tightly. In so doing, FS altered one of its codes, and AQ didn't handle that change properly, causing AQ to crash when trying to display a record with this situation. Fixed.
  • Other minor fixes were made.

Changes in Build 26 (4/8/2015)

Enhancements to General Features
  • Database Check/Repair: Several improvements were made to the check/repair, so that AQ would find and fix additional issues. This includes a new check for file header integrity each time a file is opened.
Bug Fixes to General Features
  • Notes Screen: If you hovered your mouse over a menu item, sometimes the text of the menu item would double-print, causing a cosmetic annoyance. Fixed.
  • Multimedia Scrapbook Page: If you showed this page (showing up to 6 images on a screen) on a secondary monitor, pictures wouldn't show correctly. Fixed.
  • Change Log: Occasionally, when viewing an item in the change log, AQ would crash. Fixed.
Enhancements to FamilySearch Features
  • Updating Names: If local name matched an alternate name in FSFT, AQ wouldn't let you send it as preferred name. Now it will.
  • Updating Places: In the 'Review' screen, if a local place name matched the standardized name of FSFT, even though the displayed name was different, it would show the places as a match, and you would not be allowed to update the name. For example, if the place name in both your file and the unseen standardized place name in FSFT was, "Gary, Lake, Indiana, United States", but the name displayed in FSFT was, "Gary, Indiana" AQ would see this as a match and preclude you from updating the FSFT value. AQ now sees this as a different place and allows you to update it.
  • Display of FSFT Data: AQ had been showing place names from FSFT after cleaning them up. IE: "New York,New York" would be shown as "New York, New York" (notice that a space was added after the comma.) Now AQ shows places as they are shown in FSFT.
  • Syncing Dates: FSFT recently made a change in the way they expect dates, from a 3 month standard month (ie 12 Apr 2015) to the full month (ie 12 April 2015). Dates are now sent to FSFT in this format.
  • Syncing Places: When sending place names to FSFT, standardized names are sent along with the name as you have it entered.
  • Import Family Lines: Some minor adjustments were made between AQ and FSFT to make syncing more smooth, including allowing the import of family lines to continue when certain errors were returned from FSFT during the process.
Bug Fixes to FamilySearch Features
  • Import Family Lines: If you imported descendants for a person, and AQ encountered a situation where there was no relationship with a spouse, yet the couple had children, only the ID of the spouse and children were loaded. Now the names and standard events are imported.
  • Other minor fixes were made.

Changes in Build 24 (1/17/2015)

Bug Fixes to FamilySearch Features
  • Review/Sync Individual Screen: In build 23, a bug was introduced in which you were not able to download the LDS ordinances of Confirmation or Initiatory from FamilySearch Family Tree to your file on this screen. Fixed.

Changes in Build 23 (1/10/2015)

Bug Fixes to General Features
  • Various Minor Fixes
Enhancements to FamilySearch Features
  • Upcoming Changes: FamilySearch is planning to change how AQ and other similar products communicate with it in the near future. Adjustments were made so that AQ will handle the most imminent changes well. If you use the features in AQ that sync with FamilySearch Family Tree, you will need to update to new builds as they are announced. The changes to this build include:
    1. Sometime on or after 1/14/2015, FamilySearch will remove a method that AQ has used in reconciling LDS ordinance batches. This build no longer relies on that method. Batches will still reconcile, but AQ will no longer be able to detect the FOR ID for some batches.
    2. FamilySearch has announced that it will turn off access to new.FamilySearch (nFS) on Feb 1, 2015. This build contains the ability to gracefully handle that event when it happens, whether on Feb 1 as announced, or later if this action is delayed. Between the release of this build and the time that nFS is terminated, you should see no difference. After nFS is terminated, you will still continue to sync with FamilySearch Family Tree, but will no longer be able to see the additional data from nFS.
      For users who have not been using the capability to 'Show nFS Data', they will see no difference after nFS is terminated. The termination of nFS will only be noticed by users who have been taking advantage of viewing this extra data.
Bug Fixes to FamilySearch Features
  • Various Minor Fixes

Changes in Build 22 (11/22/2014)

Bug Fixes to FamilySearch Features
  • Login: If you had set the login option to automatically login as needed, AQ crashed. This had worked in all earlier versions, but was broken in build 21, then rectified a few hours later in build 22.

Changes in Build 21 (11/21/2014)

Enhancements to General Features
  • Source Entry: Some minor tweaks were made to simplify the process of entering the first source for a person.
  • Ancestry.com Adjustment: Over the last couple of years, Ancestry.com has removed support for certain direct access from Ancestral Quest. With this build, AQ has removed some links to Ancestry.com that relied on those services. You can still use the links in the Pedigree View of AQ to do general searches on Ancestry.com, but the 'Direct Links' to more refined search results have been removed.
  • Minor Tweaks: Some other minor adjustments were made and minor bugs were fixed.
Enhancements to FamilySearch Features
  • Upcoming Changes: FamilySearch is planning to change how AQ and other similar products communicate with it in the near future. Adjustments were made so that AQ will handle the most imminent changes well. If you use the features in AQ that sync with FamilySearch Family Tree, you will need to update to new builds as they are announced. The changes to this build include a new method of logging into FamilySearch (you won't see any difference, but the technical method for establishing the connection between AQ and FamilySearch has been replaced), uploading deceased records which have no death data (these people will be considered as 'Living' by FamilySearch Family Tree in the near future if you continue to use older builds of AQ), and the method for Reconciling batches of LDS Temple Ordinances has been rewritten to avoid using methods that FamilySearch will retire at the end of November, 2014. You shouldn't notice any difference in these functions as long as you update to this build before FamilySearch implements the changes.
  • Mark All: On AQ's screen which allows you to sync families between your personal file and FamilySearch Family Tree, there is a Mark All button which, in some situations, will allow you to mark all of the children of a FamilySearch family to be downloaded to your file. In the past, when you used this, it downloaded the child and the type of relationship between the child and the parents, but it did not automatically download the Sealing to Parents for LDS users. It now downloads the Sealing to Parents ordinance for LDS users.
  • Restoring Changed Data: FamilySearch has changed the way they inform AQ that users can restore changes shown in the Change History. AQ has been updated to the new method.
  • Helper: FamilySearch had made some changes recently that caused the Helper function to not work in some instances. We expect FamilySearch to remove this function completely in the near future, but for now AQ has been adjusted to continue to allow you to sign in as a helper.
Bug Fixes to FamilySearch Features
  • Update after Link: In some situations, after you downloaded data from FamilySearch Family Tree to the record in your personal file, the downloaded data didn't show immediately, due primarily to screen refresh issues. Fixed.
  • Upload of Nickname: If you uploaded a nickname with multiple parts, such as "Jim Bob" rather than simply "Jim" or "Bob", FamilySearch would reject it. Fixed.

Changes in Build 20 (5/29/2014)

Enhancements to General Features
  • Check Repair: Made improvements to find and fix some additional issues.
  • Translations: Added some comments to some abbreviated labels to help translators with the translations.
Bug Fixes to General Features
  • Web Page Creation: When creating a web page, if you asked for living descendants, but wanted to show “Living” rather than the name, this worked fine for the descendant, but if a spouse was living, it showed the name of spouse. Fixed. Now shows “living” for a living spouse.
  • Book Reports: If you had pictures for people, there was a small chance that the page break would lose a few words. Fixed.
Enhancements to FamilySearch Features
  • Upcoming Changes: FamilySearch is planning to change how AQ and other similar products communicate with it in the near future. Adjustments were made so that AQ will handle these changes well.
  • Entering of IDs: In the last week or two, FamilySearch changed the way IDs could be sent, so that if you entered "jk2z-n2g" instead of "JK2Z-N2G", this no longer worked. AQ was adjusted to compensate for this change, so you can still enter "jk2z-n2g" and AQ will change it for you.
Bug Fixes to FamilySearch Features
  • Link Screen: The 'Link Bar', containing some edit options for couples, was visible during the matching process. This was in error. Removed.
  • Update Ordinances: If a person died before 8 according to the local data, yet the Seal to Parents was not yet recorded in the local file, the Update Ordinances could possibly duplicate the LDS Confirmation and Initiatory ordinances. Fixed.
  • Family Sync: If you download parents from this screen, the individual LDS ordinances of Baptism and Endowment were not imported. Fixed.

Changes in Build 19 (3/3/2014)

Enhancements/Bug Fixes to General Features
  • Language Support: Simplified the process of downloading and installing non-English language modules, and made it possible for AQ to alert users of these modules when updates to the language modules have been posted.
  • Using AQ at LDS Family History Centers: AQ has a feature that allows a user to password protect its files on a machine, so that if grandchildren are allowed to explore their grandparent's work, they will only be able to view the data, and not change it. This feature has been disabled for the FHC version to alleviate a possibility of locking AQ on that machine.
Enhancements to FamilySearch Features
  • General: In many situations, AQ is now faster at loading information from Family Tree, so some screens will come up more quickly.
  • Import Family Lines: Found ways to significantly speed up the importing of siblings of ancestors, when you are not importing spouses of these siblings. Also implemented an alternate method of downloading descendants that is significantly faster.
  • Merging FT Records: When merging Family Tree records from the "Link With FamilySearch" screen, AQ is now significantly faster at displaying the Merge screen.
  • Upload Notes: In build 18, when you uploaded records from your file to Family Tree, and asked AQ to also upload notes, or when you uploaded notes for a group of records, AQ uploaded all notes for each selected individual, including confidential notes. An adjustment was made so that confidential notes will not be uploaded in these situations.
Bug Fixes to FamilySearch Features
  • Link Screen: On the "Link With FamilySearch" screen, we introduced a bug in build 18, wherein after you merge two records in Family Tree, this screen didn't allow you to then link your record to a Family Tree record. You had to exit the screen and come back to it to reset it. Fixed.
  • Import of Descendant Family Lines: In build 18, the marriage date/place for couples was not being imported. Fixed.

Changes in Build 18 (1/22/2014)

Enhancements/Bug Fixes to General Features
  • Sorting: If you sort by Custom ID on the Name List screen or the Custom Report, purely numeric IDs should sort as numbers and IDs that are not purely numeric should sort alphabetically. AQ had a bug wherein if an ID was a number of more than 5 digits, the number was sorted alphabetically. Fixed. All numeric IDs now sort numerically.
Enhancements to FamilySearch Features
  • Import Family Lines: You can now import descendants of an ancestor from Family Tree. Since you typically already have some descendants of any given ancestor, this function will fill in descendants that you were missing, while leaving alone the descendant records that you already have. (We recommend making a backup of your database before using this feature, as you don't know what records you will get.)
  • Upload Notes When Uploading Individuals: When you upload records from your file to Family Tree, AQ used to also add the notes. During the switchover from nFS to Family Tree, notes were not available in Family Tree until recently, so this capability had been removed. Now that Family Tree can handle notes, this capability has been restored.
  • Upload Notes for Groups: You can now select a group of individuals in your database and have AQ scan the corresponding records in Family Tree. If your notes are not yet in Family Tree, you can quickly upload them. (There is a new Upload Notes option on the FamilySearch menu for this.)
  • Delete Couple Relationships: You can now delete couple relationships in Family Tree. If children are involved, you will be asked whether to have the children remain linked with the father, with the mother, or with both individually. At the time this feature is introduced (1/22/2014), AQ is the only software, including Family Tree, that can split couple relationships when they have children.
  • Delete Parent/Child Relationships: You can now remove children from parents in Family Tree.
  • Sync Marriage Notes: You can now exchange notes between marriages in your file and Family Tree.
  • Enhancements to Notes Sync Screen: The notes sync screen can now be enlarged, and you can more easily move text from the local notes to FT notes and vice versa.
  • Merge Relatives: When working in the Family Sync screen, buttons have been added to Merge Fathers, Merge Mothers, Merge Spouses, Merge Children and Merge Siblings. When working with families, and you notice that Family Tree has duplicates of any of these relatives, you can merge them immediately.
  • Link Screen: On the "Link With FamilySearch" screen, when you find a record in Family Tree that matches your local person, you have been able to check a box next to the Family Tree record to indicate that the person is a match. This build adds the ability to use a button at the bottom of the screen to Mark or Unmark the record as a match. You can use whichever method is more intuitive for you.
  • Download LDS Ordinances Screen: We found some cases where the temple records show sealings to people who are still in nFS, but no longer in Family Tree. Because AQ works now with FT, these should not be shown, and AQ has been enhanced to not show these.
Bug Fixes to FamilySearch Features
  • Sign in as Helper: In Build 17, we broke the ability to sign in as a helper. Fixed.

Changes in Build 17 (12/19/2013)

Enhancements/Bug Fixes to General Features
  • None: This build implements improvements to AQ's interface with FamilySearch only.
Enhancements to FamilySearch Features
  • Import Family Lines: Importing of ancestors now properly reads information from Family Tree. You will find that it creates a faithful reproduction of the ancestry as found on FamilySearch Family Tree with one exception: if a child is recorded as his own parent in Family Tree, AQ will not import such a parent. Due to the difference in the way Family Tree shares LDS ordinance information vs the way nFS shared it, the import is now a two step process. First it will import the records of individuals and relationships, and then, if you are signed into FamilySearch with and LDS account, it will import the LDS ordinances. If you prefer to not import the LDS ordinances, you can cancel this second phase of the import.
  • Update LDS Ordinances: The Update Ordinances feature now allows you to skip the verification of FamilySearch IDs, thus speeding up the process. (But if you skip this verification, ordinances will not be updated for any records whose IDs have changed in Family Tree.)
Bug Fixes to FamilySearch Features
  • Review/Sync Individual Screen: In build 16, a new Link Bar was introduced to the top of this screen. For some rare situations, the links were not active. Fixed.
  • Family Sync Screen: If there is no relationship between two people, but a child indicates that they are both parents, AQ was not showing them as a couple. It now does, to provide the same display as shown in FamilySearch Family Tree.

Changes in Build 16 (11/14/2013)/H4>

Enhancements to FamilySearch Features
  • Sources: On the Review/Sync Family screen, you can now see all sources for couples from both Family Tree and your local file. You can also exchange these sources between your personal file and the couple records of Family Tree.
  • Change History: A new link on the Review/Sync Individual screen allows you to see all changes that have been made to a person record in Family Tree. Also, if you are examining the details of any fact, you will be able to see the changes made to just that fact, and have an option to restore older facts.
  • Review/Sync Individual Screen: Several buttons were moved from the bottom of the screen to a menu bar near the top of the screen to improve readability of this screen. Also, the "Select Family Tree" button was renamed to be an "Import from nFS" link to better reflect its current use.
  • Notes: You can now view notes from Family Tree on the Review/Sync Individual screen, and a Notes button allows you to exchange notes between your personal records and the records of Family Tree.

Changes in Build 15 (10/21/2013)

Enhancements to General Features
  • Sources: If you attached an object other than a picture to a citation (such as a document, audio clip, web page), the path/URL of this object will now be displayed where the thumbnail of of an image would otherwise be displayed if it were a picture.
General Bug Fixes
  • Web Page Creation: If the image to a source is located on the Internet rather than on your system, the link to the image was not created properly. Fixed.
Enhancements to FamilySearch Features
  • Sources: On the Review/Sync Person screen, you can now see all sources from both Family Tree and your local file. You can also exchange these sources between your personal file and the record of Family Tree.
  • Source: Sources in Family Tree which are tagged to the "Name" or "Gender" facts can now be transferred to the local record. Conversely, records attached to the local record can now be accessed via the source icon next to the Name fact, and transerred to the record in Family Tree.
Bug Fixes to FamilySearch Features
  • Merge: After you completed a merge for two Family Tree records, AQ might crash. Fixed.

Changes in Build 14 (09/21/2013)

Enhancements to General Features
  • Sources: If you attached an object other than a picture to a source (such as a document, audio clip, web page), the path/URL of this object will now be displayed where the thumbnail of of an image would otherwise be displayed if it were a picture.
  • Check/Repair: Check/Repair now finds and fixes a couple of other types of problems.
General Bug Fixes
  • Notes: If notes contained non-English characters, and one of these was positioned in just the right place, it might be displayed as two blocks. Fixed.
Enhancements to FamilySearch Features
  • Sources: On the Review/Sync Person screen, you can now see sources from both Family Tree and your local file if they are attached to events/facts. You can also exchange these sources between your personal file and the record of Family Tree.
  • Merging Family Tree Records: You can now see a summary of the information for the local matching person while you make decisions about which items to keep or discard when merging two Family Tree records.
  • Merging Family Tree Records: Improved handling of the "Not A Match" in Family Tree.
  • Review/Sync Person Screen: If your local person has notes, these are now shown on this screen.
Bug Fixes to FamilySearch Features
  • Import Family Lines: The Marriage data between ancestral couples was not being imported. Fixed.
  • Various: Some other minor bugs were fixed.

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. Fixed.
  • 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.

Changes in Build 12 (06/29/2013)

Enhancements to FamilySearch Features
  • Merging Family Tree Records: Added a Merge capability for merging records on Family Tree.
  • Discussions: Converted the feature which reads and updates Discussions on FamilySearch to directly work with Family Tree rather than New.FamilySearch.
Bug Fixes to FamilySearch Features
  • Syncing Familes: For some advanced methods of linking families together on Family Tree from within AQ, AQ sometimes gave error messages after the links were complete. Fixed.

Changes in Build 11 (06/22/2013)

Enhancements to FamilySearch Features
  • Individual Review with FamilySearch Screen: Added ability to delete facts from individual records of Family Tree.
  • Check for Changes: Added an option to "Mark All" changed records as having been reviewed.
Bug Fixes to FamilySearch Features
  • Updating PIDs: AQ detects in more places when the PID has changed on Family Tree, and appropriately either updates the link in your personal file, or removes the link with the FamilySearch person when the FamilySearch person was deleted.
  • Check for Changes: When you "Reviewed" a record, it wasn't being marked as reviewed. Fixed.
  • Adding Records to Family Tree: Family Tree is not yet showing Notes for individuals, so AQ has temporarily removed the features dealing with syncing notes. If you attempted to add a person to Family Tree, and used the option to upload everything about the individual including notes, and if the person had notes, AQ attempted to send the notes improperly, so the person would not be added to Family Tree. Fixed. (AQ does not attempt at this time to send the notes.)

Changes in Build 10 (06/18/2013)

Enhancements to FamilySearch Features
  • General: Changed most of the API calls that used to work with New.FamilySearch.org to work instead with the Family Tree of FamilySearch. (NOTE: If you are working with the FamilySearch features, you will need to upgrade to this build or later before June 30, 2013, as your old copy of AQ will stop working with FamilySearch on that date. If you are not working with AQ's features that coordinate with FamilySearch, you do not need to upgrade to this build.)

Changes in Build 9 (03/20/2013)

General Bug Fixes
  • Reorder Spouses/Children: Occasionally, AQ would crash after you reordered spouses or children. Fixed.
Bug Fixes to FamilySearch Features
  • General: In a very rare case, AQ would crash after receiving unexpected data from nFS. Fixed.
  • Set Family Tree: Sometimes, if you tried to set a place to Family Tree, when the place included a missing jurisdiction (for example, "Mesa, , Arizona" rather than "Mesa, Maricopa, Arizona", the new place would be set to nFS, but not to Family Tree. Fixed.
  • Seal to Parents: In build 8, we introduced a bug into AQ, in which it would occasionally indicate that there was an extra set of parents. Fixed.
  • Long Place Name: Sometimes, if you tried to send a Place name to nFS or Family Tree which was more than 60 characters long, only the first 60 characters would be sent. Fixed.

Changes in Build 8 (02/27/2013)

General Bug Fixes
  • Descendant Dropline Chart: If you asked for all boxes on a generation to be the same size, AQ actually only made the boxes for a given family to be the same size. Now it makes all boxes for all families on that generation to be the same size.
  • Descendant Dropline Chart: If a descendant had children, but no spouse, the grouping of child boxes were not placed on the chart in the proper position. Fixed.
  • Notes Screen: In build 7, a change was made to keep the Notes screen from getting locked into full screen mode. A random situation was discovered that could still temporarily cause this. Fixed.
  • GEDCOM Import: A very rare situation was encountered that caused AQ to not import one file correctly. Fixed.
Enhancements to FamilySearch Features
  • Combine/Merge: FamilySearch has requested that users no longer use commercial programs such as AQ to combine records in nFS, but rather to use the Merge of Family Tree. AQ will no longer allow combines, but will still help you identify duplicates, and set up the Family Tree merge screen, so all you have to do is click the 'Merge' button (or equivalent) in Family Tree. (Note: Eventually FamilySearch will allow AQ to actually do the Merge.)
Bug Fixes to FamilySearch Features
  • AQ Hangs Randomly: About Feb 15, 2013, FamilySearch broke something, which caused AQ to hang on random occasions. A work-around has been implemented, so that AQ should no longer hang when FamilySearch becomes unresponsive.
  • Update Ordinances: If the status of a sealing (SP or SS) was "Submitted", AQ treated it as if completed, so it wouldn't update these sealings. Fixed.
  • Set Family Tree: Sometimes, AQ didn't show all of the variants of names for you to choose. Fixed.
  • Manage Batches: if the local ordinance showed, "Sub (date)", and the Temple system showed "reserved", the ordinance was shown as needing to be updated, and would update. Since "Submitted" in the local file is the same as "Reserved" in FamilySearch, this was in error. It now works properly.

Changes in Build 7 (11/06/2012)

General Enhancements
  • Notes Screen: The Notes screen would get locked into full screen mode for many users. A change was made so that the user can stretch the Notes screen larger or smaller, but can no longer maximize the screen. This will keep the screen from locking in maximized position.
  • Database Check/Repair: Now fixes a rare problem with an internal ID called a 'GUID'.
General Bug Fixes
  • Family Group Report: Depending on how some options were set, a bug caused the program to crash when the FGR was selected. Fixed.
  • Dropline Descendant Chart: The option to make all the boxes in a generation be the same height was not working properly. Fixed.
  • GEDCOM Export: If you added a folder to the scrapbook of an individual, and set the export option to embed scrapbook items, the GEDCOM file would not be completely written, causing it to not import properly later. Fixed.
  • Convert from Older File: Due to the addition of Color Coding, if you tried to convert an older database while on the Family View, AQ would give lots of bogus error messages during this type of database conversion. Fixed.
  • Generating IDs: Sometimes, when you used the 'Generate IDs' in the Tools menu, one of the records being displayed on the Family View would not seem to be changed. Fixed.
  • Translation Modules: Some translated items on the Family View were not carried over when a new build of AQ was released, and had to be re-translated. Fixed.
Enhancements to nFS Features
  • Set Family Tree: The 'Set Summary' button on the Review Individual with FamilySearch screen was changed to 'Set Family Tree' to keep up with changes in the FamilySearch system.
  • Timeout: After about one half hour, if you were logged into FamilySearch but didn't do anything that caused AQ to work with FamilySearch, the FamilySearch system terminates your session. If you later caused AQ to work again with FamilySearch, AQ would ask if you wanted to log in. It no longer asks, but simply starts the login process.

Changes in Build 6 (08/29/2012)

Bug Fixes to nFS Features
  • Review Individual with FamilySearch Screen: LDS users relied on a new temple icon on this screen next to the Sealing to Spouse and Sealing to Parents ordinances to allow them to download these sealings from the FamilySearch system. This icon was available even when there were no spouses or parents in the personal database, but it should not have been. Fixed.

Changes in Build 5 (08/28/2012)

General Bug Fixes - (Note that the single fix in this build affects only users who still have a version 12/12.1 key, not those who have upgraded to version 14. If you have version 14, and have already updated to build 4, you do not need this build.)

  • Reports in AQ 14 for Users of AQ 12.1: The list reports that were blocked in AQ Basics, but were part of AQ 12.1, were supposed to still be available to those with a key for 12.1 while using AQ 14. In AQ 14.0 build 4, the printing of these reports was fixed. With build 5, the preview of these reports for those with a version 12/12.1 key was also fixed.

Changes in Build 4 (08/27/2012)

General Enhancements
  • Color Coding: Color coding is now on the Name List view and Custom Reports.
  • Color Coding: Depending on how your database was sorted, the setting of standard color coding might be quick or quite slow. This should always be quick now, unless you are sorting on color coding in the Name List view.
  • Tags: Tags are now on the Name List view and Custom Reports.
  • Tags: Tags are now numbered to make it easier to refer to them.
  • Dual Dates: In AQ 12.1 build 34, we enhanced the handling of dual dates so that 1775/1776 was shown as 1775/6. Many users asked if we could undo that change. A new preference was added to the Formats tab of Preferences to allow you to choose whether to show the shortened or lengthened version of such a date.
  • Database Conversion: When a file was converted using the 'File|DB Converter' option, the old file was not closed, which caused confusion for some users. It now closes so that only the newly converted file is still open.
  • PAF Database Limitations: Our literature described which features were not available for a PAF DB, and the menu items were dimmed, but many users with a PAF DB were confused. Menu items are no longer dimmed, but a message about the limitation now shows when the option is selected.
General Bug Fixes
  • Reports in AQ 14 for Users of AQ 12.1: The list reports that were blocked in AQ Basics, but were part of AQ 12.1, were supposed to still be available to those with a key for 12.1 while using AQ 14. This was broken. Fixed.
  • General Bug: We found a situation that could cause AQ to quit working seemingly at random. That bug was fixed.
  • Marriage Screen: For users who had turned off the LDS data, the Relationship (Marriage) screen was supposed to get smaller because there was less data to show, but instead it became larger. Fixed.

Bug Fixes to nFS Features

  • Linking Parents: If, on the Family Sync w/ FamilySearch screen, you tried to link a parent in FS with a person who was in the local file, but not linked as a parent in the local file, AQ would hang. Fixed.
  • LDS Sealings: If LDS Data was enabled, the new option to allow you to download LDS sealings from the Individual Review w/ FamilySearch screen was only supposed to let you download ordinances when there was a spouse or set of parents in your local DataBase. The screen was sometimes available when it shouldn't be, causing confusion. Fixed.

Changes in Build 3 (07/5/2012)

General Bug Fixes
  • Pedigree View/Color Coding: If you had assigned any color coding to anyone in your file, the colors for name boxes were to be set to black text on either a white background or the color coded background. Sometimes the text was not properly set to black for this situation. Fixed.
  • Color Coding: If you used the option to 'Clear all colors', the colors were cleared, but the count was not reset to 0. As a result, if you had a color scheme for names as something other than black text on white background, your color scheme was not restored. Fixed.

Bug Fixes to nFS Features

  • Update Ordinances: If you were using a PAF database which was created by PAF rather than by AQ, and you used the automatic update of all ordinances with the option to include LDS Confirmations, this worked fine the first time, but if you ran it a second time, the process might duplicate the LDS Confirmation ordinances. Fixed.

Changes in Build 2 (6/29/2012)

  • Builds 0-2 were the first commercially available builds. Minor, unlisted changes were made between these builds.

module content icon