Gaylon,

We took care of a bunch of sealings yesterday and today, I used the
Update Ordinances function in the Ordinance Reservation and Tracking
System. Not one of the sealings was picked up. This function does not
work on either couple -or- child to parent sealings.

I had to use Manage Batches, do a reconciliation and then review all
to pick up the changes. Then update all local took care of the
individual records.

Thank you for looking into this for us,

Tom


On Thu, 31 Jan 2013 23:42:03 -0700, you wrote:

>
>
>Still looking for a reason why sealings are not being updated in the "Update
>Ordinances" action under Ordinance Reservation and Tracking system.  Please
>see my post of a couple of days ago.  Thanks in advance.
>
>
>
>S Douglas Cline
>
>Cell:  801 560-2340
>
>
>
>
>
>[Non-text portions of this message have been removed]

Gaylon, I also have been seeing frequent crashes with the current build of
AQ. My circumstances are different than Hal's. I see the crash when I sort
the children in order of age. Once I have ordered the children and hit ok
the program gives me the "AQ has stopped working" error and shuts down.
When I restart it the sorting has been accomplished successfully. I am
using Win 7 as my OS.

Miles Meyer

Miles Meyer

"We're in a giant car heading toward a brick wall and everyone's arguing
over where they're going to sit." -- David Suzuki


On Sun, Feb 3, 2013 at 3:29 PM, Hal Bradley <hw.bradley@...> wrote:

> **
>
>
> Gaylon,
>
> I keep trying to prepare names for the temple but after linking one or two
> names successfully to NFS, the program then says "AQ has stopped working"
> and it shuts down. I am running 12.1.34 on Windows Vista. I have never had
> this problem before. I rebuilt my database and ran error check and it still
> crashes. Please help.
>
> Thank you.
>
> Hal Bradley
>
> [Non-text portions of this message have been removed]
>
>
>


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

I get crashes only when sorting children or spouses.


I am also using W7 and AQ 14.00.7


---- Miles Meyer <milesmeyer@...> wrote:
> Gaylon, I also have been seeing frequent crashes with the current build of
> AQ. My circumstances are different than Hal's. I see the crash when I sort
> the children in order of age. Once I have ordered the children and hit ok
> the program gives me the "AQ has stopped working" error and shuts down.
> When I restart it the sorting has been accomplished successfully. I am
> using Win 7 as my OS.
>
> Miles Meyer
>
> Miles Meyer
>
> "We're in a giant car heading toward a brick wall and everyone's arguing
> over where they're going to sit." -- David Suzuki
>
>
> On Sun, Feb 3, 2013 at 3:29 PM, Hal Bradley <hw.bradley@...> wrote:
>
> > **
> >
> >
> > Gaylon,
> >
> > I keep trying to prepare names for the temple but after linking one or two
> > names successfully to NFS, the program then says "AQ has stopped working"
> > and it shuts down. I am running 12.1.34 on Windows Vista. I have never had
> > this problem before. I rebuilt my database and ran error check and it still
> > crashes. Please help.
> >
> > Thank you.
> >
> > Hal Bradley
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Others have also reported the problem with sporadic crashes when sorting
children. Unfortunately, this is so random that we haven't been able to identify
what is causing it yet. We'll continue to keep our eye open for the underlying
cause of the problem. Some users have sent in all that we normally need to
recreate and solve the problem, but this seems to be related to something on the
computer, as we haven't yet been able to duplicate the problem on our machines.

Gaylon


----- Original Message -----
From: Leslievaughn@...
To: "AQ NFS" <AQ_NFS@yahoogroups.com>
Cc: "Miles Meyer" <milesmeyer@...>
Sent: Monday, February 4, 2013 8:14:41 AM
Subject: Re: [AQ_NFS] AQ crashes

I get crashes only when sorting children or spouses.


I am also using W7 and AQ 14.00.7


---- Miles Meyer <milesmeyer@...> wrote:
> Gaylon, I also have been seeing frequent crashes with the current build of
> AQ. My circumstances are different than Hal's. I see the crash when I sort
> the children in order of age. Once I have ordered the children and hit ok
> the program gives me the "AQ has stopped working" error and shuts down.
> When I restart it the sorting has been accomplished successfully. I am
> using Win 7 as my OS.
>
> Miles Meyer
>
> Miles Meyer
>
> "We're in a giant car heading toward a brick wall and everyone's arguing
> over where they're going to sit." -- David Suzuki
>
>
> On Sun, Feb 3, 2013 at 3:29 PM, Hal Bradley <hw.bradley@...> wrote:
>
> > **
> >
> >
> > Gaylon,
> >
> > I keep trying to prepare names for the temple but after linking one or two
> > names successfully to NFS, the program then says "AQ has stopped working"
> > and it shuts down. I am running 12.1.34 on Windows Vista. I have never had
> > this problem before. I rebuilt my database and ran error check and it still
> > crashes. Please help.
> >
> > Thank you.
> >
> > Hal Bradley
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>



------------------------------------

Yahoo! Groups Links

Hal:

The first thing you should try is to download the latest build of AQ 14. Even if
you don't want to purchase an updated registration key for AQ 14, all of the
features that you are currently using in AQ 12.1 will still work for you in AQ
14.

FamilySearch has changed some things about the way AQ "talks" to nFS, and the
newer version has adjusted for some of these changes. Your older AQ 12.1 does
not have these changes.

Each time that AQ starts, it provides you with a "Newsline" window, which has
two purposes:

1) Let you know whether you are up to date, and if not, it provides a link to
download the latest version of AQ -- please follow this link.

2) Provide you with other information we feel is important to share with you. If
you haven't watched the two new videos that are currently mentioned on the
Newsline window, you might consider watching them. If I remember correctly, the
first segment of the first video, which teaches about the new features in AQ 14,
also helps to clarify how you can use AQ 14 with a version 12 key.

Gaylon



----- Original Message -----
From: "Hal Bradley" <hw.bradley@...>
To: "AQ NFS" <AQ_NFS@yahoogroups.com>
Sent: Sunday, February 3, 2013 1:29:39 PM
Subject: [AQ_NFS] AQ crashes

Gaylon,



I keep trying to prepare names for the temple but after linking one or two
names successfully to NFS, the program then says "AQ has stopped working"
and it shuts down. I am running 12.1.34 on Windows Vista. I have never had
this problem before. I rebuilt my database and ran error check and it still
crashes. Please help.



Thank you.



Hal Bradley



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



------------------------------------

Yahoo! Groups Links

It should be noted that you cannot "unmerge" (split) combined records
in newFamilySearch. This is also not functional in Family Tree.

If you have a record that needs to be split, the only way it can be
done currently is to open a case with FamilySearch.org and indicate
the persons (including their PIDs) involved.

You should not attempt this, except in the case where two separate
people were combined into the same record and each likely has
ordinance work that has been done. I have one such case open right now
to take care of this problem: There are only two people, one with
three records and other with six, that need to be split. They were
sisters married to the same husband, and have similar given names.
Because the combined records were created in newFamilySearch, the
Family Tree instructions for splitting records do not apply.

If you have an ancestor with many, many combined records, then use
Family Tree to indicate which data is valid and why. You can delete
duplicate data as well, thus cleaning up the record in Family Tree.
Actions of this nature are not reflected back through to
newFamilySearch. You can also select which vital information (name,
dates of birth and death, and where buried) is correct through
Ancestral Quest.

Because Family Tree is still in the process of development, you can
expect the situation to change from time to time, but I thought I
would pass on what I've discovered as of this date.

Tom

Although FamilySearch has disabled the record separation function in the NFS Web
interface, the Application Program Interface (API) still works.  FamilyInsight
and/or Ancestor Split (both from Ohana Software) still can be used to separate
improperly combined NFS records.  Record separation in NFS is reflected in
FamilyTree.

Gaylon,



I have not yet heard anything about the problem that I mentioned earlier and
that Tom Huber wrote to you about concerning the Ordinance Reservation and
Tracking Systems inability to update sealing ordinances through the Update
Ordinances function.  I didn't know whether this as fallen "through the
cracks" or whether it's simply something that you're working on.  Could you
please advise as to whether this is a problem or whether AQ was never meant
to update couple or child to parent sealings?



Thanks in advance



S Douglas Cline

Cell:  801 560-2340





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

I have taken some time to look into this. I found 3 things:

1) The Update Ordinances function seems to work as designed.

2) FamilySearch is starting to have some issues with dropping the communication
between AQ and nFS. As a result, some things that in the past have run quickly,
now often run slowly, or not at all. We have let FamilySearch know of our
concern that they may have broken something recently. I have found that if a
process such as updating ordinances seems to 'hang,' that you may need to wait a
day and try again. Most of the time, things seem to work normally for me, but we
are hearing from a few users of both AQ and nFS, that some processes which no
longer complete on one day, will complete the next day.

3) One of the safeguards in the design of the Update Ordinance function may lead
a user to occasionally think that something didn't work. Here is an example:

In FamilySearch, let's say that you have:

Robert (AAA-BBBB) ==  Mary (CCC-DDDD)
                    |
                Robert Jr (EEE-FFFF)

You also have a duplicate for Robert, such that there is also:

Robert (GGG-HHHH) ==  Mary (CCC-DDDD)
                    |
                Robert Jr (EEE-FFFF)

In the Temple records, Robert Jr is sealed to Robert (AAA-BBBB) and Mary
(CCC-DDDD). But you have linked your copy of Robert Sr to (GGG-HHHH), and there
is no sealing between this record of Robert Sr and Robert Jr.

When AQ looks for Sealings -- whether spouse or child/parent -- it requires that
the links are established correctly, otherwise it will assume that the sealing
was not completed between the people in your file.

I don't know whether this example was clear enough, but I hope it helps.

In any case, the only time I saw in my testing, where a sealing was not
transferred from the Temple System to AQ through the Update Ordinance feature,
was when people were not linked correctly.

If anyone has examples of where AQ fails to update an ordinance when linkages
are correct, I would like for them to send me a backup of their database, and a
note as to which people are not being updated.

Gaylon


--- In AQ_NFS@yahoogroups.com, "S Douglas Cline" <clinesd@...> wrote:
>
>
>
> Gaylon,
>
>
>
> I have not yet heard anything about the problem that I mentioned earlier and
> that Tom Huber wrote to you about concerning the Ordinance Reservation and
> Tracking Systems inability to update sealing ordinances through the Update
> Ordinances function.  I didn't know whether this as fallen "through the
> cracks" or whether it's simply something that you're working on.  Could you
> please advise as to whether this is a problem or whether AQ was never meant
> to update couple or child to parent sealings?
>
>
>
> Thanks in advance
>
>
>
> S Douglas Cline
>
> Cell:  801 560-2340
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

On Wed, 20 Feb 2013 01:03:28 -0000, you wrote:

>If anyone has examples of where AQ fails to update an ordinance when
linkages are correct, I would like for them to send me a backup of their
database, and a note as to which people are not being updated.
>
I have run into numerous instances where I run Update Ordinances and
some very old ordinances are suddenly "found" and the records updated.
I've always attributed these to continued updates of the data from
previously non-included records.

I have a very large database and several areas seem to fail to update
as intended. One of them is after I've reserved a record, AQ puts in
submitted (with date), but the Update Ordinances fails to Update from
"Submitted (with date)" to "In process". Keep in mind that this may
because I have not printed a FOR or had cards printed for the
ordinances.

I've also seen instances where I run the "Manage Batches", reconcile,
and update all. I do not do anything with the Update or Update Local
functions, but would rather leave it to Update Ordinances to handle.
They don't always do the job and I can come back (after shutting down
AQ, recycling the computer) and still see the fields with an asterisk,
indicating that it needs to be updated with my local records.

Because we are moving toward Family Tree, I haven't taken time to
report the problem because I feel that working on some of these at
this time may not be the best use of time. If I'm wrong, I'll do the
research and report back privately with a copy of the database and
also the PIDs and RINs of those impacted.

Tom


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

Gaylon -



I have been attempting to use this function to update ordinances of sealing
to parent and spouse for months (perhaps 7 or 8).  It has never worked.  I
don't feel this is a new thing..



S. Burger



From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On Behalf Of
gfindlay@...
Sent: Tuesday, February 19, 2013 6:03 PM
To: AQ_NFS@yahoogroups.com
Subject: [AQ_NFS] Re: updating ordinances





I have taken some time to look into this. I found 3 things:

1) The Update Ordinances function seems to work as designed.

2) FamilySearch is starting to have some issues with dropping the
communication between AQ and nFS. As a result, some things that in the past
have run quickly, now often run slowly, or not at all. We have let
FamilySearch know of our concern that they may have broken something
recently. I have found that if a process such as updating ordinances seems
to 'hang,' that you may need to wait a day and try again. Most of the time,
things seem to work normally for me, but we are hearing from a few users of
both AQ and nFS, that some processes which no longer complete on one day,
will complete the next day.

3) One of the safeguards in the design of the Update Ordinance function may
lead a user to occasionally think that something didn't work. Here is an
example:

In FamilySearch, let's say that you have:

Robert (AAA-BBBB) == Mary (CCC-DDDD)
|
Robert Jr (EEE-FFFF)

You also have a duplicate for Robert, such that there is also:

Robert (GGG-HHHH) == Mary (CCC-DDDD)
|
Robert Jr (EEE-FFFF)

In the Temple records, Robert Jr is sealed to Robert (AAA-BBBB) and Mary
(CCC-DDDD). But you have linked your copy of Robert Sr to (GGG-HHHH), and
there is no sealing between this record of Robert Sr and Robert Jr.

When AQ looks for Sealings -- whether spouse or child/parent -- it requires
that the links are established correctly, otherwise it will assume that the
sealing was not completed between the people in your file.

I don't know whether this example was clear enough, but I hope it helps.

In any case, the only time I saw in my testing, where a sealing was not
transferred from the Temple System to AQ through the Update Ordinance
feature, was when people were not linked correctly.

If anyone has examples of where AQ fails to update an ordinance when
linkages are correct, I would like for them to send me a backup of their
database, and a note as to which people are not being updated.

Gaylon

--- In AQ_NFS@yahoogroups.com <mailto:AQ_NFS%40yahoogroups.com> , "S Douglas
Cline" wrote:
>
>
>
> Gaylon,
>
>
>
> I have not yet heard anything about the problem that I mentioned earlier
and
> that Tom Huber wrote to you about concerning the Ordinance Reservation and
> Tracking Systems inability to update sealing ordinances through the Update
> Ordinances function. I didn't know whether this as fallen "through the
> cracks" or whether it's simply something that you're working on. Could you
> please advise as to whether this is a problem or whether AQ was never
meant
> to update couple or child to parent sealings?
>
>
>
> Thanks in advance
>
>
>
> S Douglas Cline
>
> Cell: 801 560-2340
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





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

All:

Over the last couple of weeks, we have heard that many of you are finding that
AQ seems to hang a lot when working with nFS. Apparently, as FamilySearch is
making changes toward implementing Family Tree, they broke something in nFS,
causing AQ to hang while waiting for nFS to respond to AQ's requests for data.

We have just put out a patch file that should fix this.

The patch file also fixes a problem with AQ's new "Update Ordinances" feature
not updating Sealings when the local database has "Submitted" or "In Progress"
for the ordinance status.

At the request of FamilySearch, we are disabling the "Combine" capability for
FamilySearch records until we have the ability to Merge in Family Tree. This
patch will disable the Combine.

You can download the patch here:

http://www.inclinesoftware.net/files/Latest.zip

Extract the contents of this file into your AQ 14 program folder. If you
successfully replace the old file, the date in the About screen of AQ will show
2/21/13.

Gaylon

For those of us uncertain as to exactly how to extract the contents of the
file INTO our AQ 14, could you give us detailed instructions?



S Douglas Cline

Brown & Young Companies

Cell:  801 560-2340





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

For Windows 7 users, the path to the AQ14 programs is:
C:\Program Files (x86)\Incline Software\Ancestral Quest 14

For other systems, you may find the path under:
C:\Program Files\Incline Software\Ancestral Quest 14

This is where you want to _save_ the downloaded file. Then unpack the
file (Most windows systems include the ability) to the same directory.
In some systems, you will need to provide adminstrator authority (for
both saving and unpacking/overwriting the files).

After you've unpacked the software, start AQ. Go to Help... About
Ancestral Quest... and look at the date at the top of the window that
opens. If you did unpacked the patch correctly, you will see the
2/21/2013 date.

On Fri, 22 Feb 2013 11:19:51 -0700, you wrote:

>
>
>For those of us uncertain as to exactly how to extract the contents of the
>file INTO our AQ 14, could you give us detailed instructions?
>
>
>
>S Douglas Cline
>
>Brown & Young Companies
>
>Cell:  801 560-2340
>
>
>
>
>
>[Non-text portions of this message have been removed]

For those of you wondering, there should be two files found in Gaylon's
link.  The first is AncQuest and the other is AQ.1033Lng.  Simply highlight
the files, right click, copy and then paste them in your AQ14 folder.  You
will receive a message to copy and replace each file.  Select copy and
replace and you should be fine.  However, you virus software may not
recognize your AQ now that you have the new files installed since they
weren't installed through an AQ update.  In this case uncheck the box in the
virus checker to not ask the question each time that AQ is initialized.



Hope this helps.



S Douglas Cline

Brown & Young Companies

Cell:  801 560-2340





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

All:

We just released build 8 of AQ 14. This was an urgent release, primarily to fix
the bug introduced by FamilySearch a couple of weeks ago, that causes AQ to
randomly 'hang' while working with nFS. There are a few other fixes as well.

To see a list of the changes, and the link to update to this build, go to AQ's
"Help" menu and click on "NewsLine".

Gaylon




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

Gaylon, I just ran this and kept getting the error message:  String -
PRODUCT NAME was not found in String Table.  This came up about a dozen
times during various parts of the install.



From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On Behalf Of
Gaylon Findlay
Sent: Thursday, February 28, 2013 2:09 PM
To: AQ NFS
Subject: [AQ_NFS] New Build of AQ 14





All:

We just released build 8 of AQ 14. This was an urgent release, primarily to
fix the bug introduced by FamilySearch a couple of weeks ago, that causes AQ
to randomly 'hang' while working with nFS. There are a few other fixes as
well.

To see a list of the changes, and the link to update to this build, go to
AQ's "Help" menu and click on "NewsLine".

Gaylon

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





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

Mary-Theresa:

Before announcing this build, we tested the installer, and it worked as
expected. I am curious as to whether others are installing without
trouble, or whether this is something specific to your machine.

Maybe you could try downloading the file again, just in case your
Internet connection had trouble during the download, and install again.

Gaylon


On 2/28/2013 3:04 PM, Mary-Theresa Dameron wrote:
> Gaylon, I just ran this and kept getting the error message:  String -
> PRODUCT NAME was not found in String Table.  This came up about a dozen
> times during various parts of the install.
>
>
>
> From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On Behalf Of
> Gaylon Findlay
> Sent: Thursday, February 28, 2013 2:09 PM
> To: AQ NFS
> Subject: [AQ_NFS] New Build of AQ 14
>
>
>
>
>
> All:
>
> We just released build 8 of AQ 14. This was an urgent release, primarily to
> fix the bug introduced by FamilySearch a couple of weeks ago, that causes AQ
> to randomly 'hang' while working with nFS. There are a few other fixes as
> well.
>
> To see a list of the changes, and the link to update to this build, go to
> AQ's "Help" menu and click on "NewsLine".
>
> Gaylon
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Just finished update to new build worked just fine, no problems



________________________________
  From: Gaylon Findlay <gfindlay@...>
To: AQ_NFS@yahoogroups.com
Sent: Thursday, February 28, 2013 6:58 PM
Subject: Re: [AQ_NFS] New Build of AQ 14

Mary-Theresa:

Before announcing this build, we tested the installer, and it worked as
expected. I am curious as to whether others are installing without
trouble, or whether this is something specific to your machine.

Maybe you could try downloading the file again, just in case your
Internet connection had trouble during the download, and install again.

Gaylon


On 2/28/2013 3:04 PM, Mary-Theresa Dameron wrote:
> Gaylon, I just ran this and kept getting the error message:  String -
> PRODUCT NAME was not found in String Table.  This came up about a dozen
> times during various parts of the install.
>
> 
>
> From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On Behalf Of
> Gaylon Findlay
> Sent: Thursday, February 28, 2013 2:09 PM
> To: AQ NFS
> Subject: [AQ_NFS] New Build of AQ 14
>
> 
>
>   
>
> All:
>
> We just released build 8 of AQ 14. This was an urgent release, primarily to
> fix the bug introduced by FamilySearch a couple of weeks ago, that causes AQ
> to randomly 'hang' while working with nFS. There are a few other fixes as
> well.
>
> To see a list of the changes, and the link to update to this build, go to
> AQ's "Help" menu and click on "NewsLine".
>
> Gaylon
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>



------------------------------------

Yahoo! Groups Links



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

Did the update and have been using the program for 3 hours. No problems.

Miles

Miles Meyer

"We're in a giant car heading toward a brick wall and everyone's arguing
over where they're going to sit." -- David Suzuki


On Thu, Feb 28, 2013 at 7:15 PM, William Knight
<williamknight57@...>wrote:

> **
>
>
> Just finished update to new build worked just fine, no problems
>
> ________________________________
> From: Gaylon Findlay gfindlay@...>
> To: AQ_NFS@yahoogroups.com
> Sent: Thursday, February 28, 2013 6:58 PM
> Subject: Re: [AQ_NFS] New Build of AQ 14
>
>
> Mary-Theresa:
>
> Before announcing this build, we tested the installer, and it worked as
> expected. I am curious as to whether others are installing without
> trouble, or whether this is something specific to your machine.
>
> Maybe you could try downloading the file again, just in case your
> Internet connection had trouble during the download, and install again.
>
> Gaylon
>
> On 2/28/2013 3:04 PM, Mary-Theresa Dameron wrote:
> > Gaylon, I just ran this and kept getting the error message:  String -
> > PRODUCT NAME was not found in String Table.  This came up about a dozen
> > times during various parts of the install.
> >
> >
> >
> > From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On Behalf
> Of
> > Gaylon Findlay
> > Sent: Thursday, February 28, 2013 2:09 PM
> > To: AQ NFS
> > Subject: [AQ_NFS] New Build of AQ 14
> >
> >
> >
> >
> >
> > All:
> >
> > We just released build 8 of AQ 14. This was an urgent release, primarily
> to
> > fix the bug introduced by FamilySearch a couple of weeks ago, that
> causes AQ
> > to randomly 'hang' while working with nFS. There are a few other fixes as
> > well.
> >
> > To see a list of the changes, and the link to update to this build, go to
> > AQ's "Help" menu and click on "NewsLine".
> >
> > Gaylon
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
> [Non-text portions of this message have been removed]
>
>
>


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

Just finished updating to build 8 and all went well.

S Douglas Cline
Brown & Young Companies
Cell:  801 560-2340

-----Original Message-----
From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On Behalf Of
Miles Meyer
Sent: Thursday, February 28, 2013 5:58 PM
To: AQ_NFS@yahoogroups.com
Subject: Re: [AQ_NFS] New Build of AQ 14

Did the update and have been using the program for 3 hours. No problems.

Miles

Miles Meyer

"We're in a giant car heading toward a brick wall and everyone's arguing
over where they're going to sit." -- David Suzuki


On Thu, Feb 28, 2013 at 7:15 PM, William Knight
<williamknight57@...>wrote:

> **
>
>
> Just finished update to new build worked just fine, no problems
>
> ________________________________
> From: Gaylon Findlay gfindlay@...>
> To: AQ_NFS@yahoogroups.com
> Sent: Thursday, February 28, 2013 6:58 PM
> Subject: Re: [AQ_NFS] New Build of AQ 14
>
>
> Mary-Theresa:
>
> Before announcing this build, we tested the installer, and it worked
> as expected. I am curious as to whether others are installing without
> trouble, or whether this is something specific to your machine.
>
> Maybe you could try downloading the file again, just in case your
> Internet connection had trouble during the download, and install again.
>
> Gaylon
>
> On 2/28/2013 3:04 PM, Mary-Theresa Dameron wrote:
> > Gaylon, I just ran this and kept getting the error message:  String
> > - PRODUCT NAME was not found in String Table.  This came up about a
> > dozen times during various parts of the install.
> >
> >
> >
> > From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On
> > Behalf
> Of
> > Gaylon Findlay
> > Sent: Thursday, February 28, 2013 2:09 PM
> > To: AQ NFS
> > Subject: [AQ_NFS] New Build of AQ 14
> >
> >
> >
> >
> >
> > All:
> >
> > We just released build 8 of AQ 14. This was an urgent release,
> > primarily
> to
> > fix the bug introduced by FamilySearch a couple of weeks ago, that
> causes AQ
> > to randomly 'hang' while working with nFS. There are a few other
> > fixes as well.
> >
> > To see a list of the changes, and the link to update to this build,
> > go to AQ's "Help" menu and click on "NewsLine".
> >
> > Gaylon
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
> [Non-text portions of this message have been removed]
>
>
>


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



------------------------------------

Yahoo! Groups Links

I just updated to to build 8. I was not having some of the issues posted on the
group. Now accessing familysearch is much, much, much slower. I constantly get
the message that familysearch is retrying when in ORTS or the synchronize
screen, then it says “cURL unable to connect AQ to FamilySearch, couldn’t
connect to host, Would you like to retry?” If I click “Retry” it often
goes and finds more information but very slowly. Is there anything I can do to
speed up the process?

Margaret

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

I am having the same issue as Margarette.

SD Cline's iPhone 5

I'm having the same issue, also
On 2/28/2013 7:30 PM, S Douglas Cline wrote:
>
> I am having the same issue as Margarette.
>
> SD Cline's iPhone 5
>
>



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

Margaret and others:

Each time you see the "FamilySearch Retrying" screen, this means that nFS has
lost the connection with AQ. Prior to build 8, this would have caused AQ to
"hang." Now that you have build 8, AQ realizes after a few seconds that nFS has
lost the connection, and it tries again, so the process continues and eventually
succeeds.

Sometimes nFS seems to be in pretty good shape, so you rarely see this
"Retrying" screen, and everything moves as quickly as you are used to. But when
nFS has a "bad hair day,", then you'll see this "Retrying" screen often, and
things will be slow, because nFS is struggling.

After seeing a few of you mention the same problem this evening, I am running
what is normally a quick process with nFS, and I see what you mean. nFS is not
doing well tonight. Maybe it will pick up in an hour. Maybe sometime tomorrow.

Build 8 didn't cause the slowness. FamilySearch is currently slow, and build 8
is helping you get through it, whereas earlier builds would have just given up.

Gaylon



----- Original Message -----
From: "Margaret Thompson" <megann-fh@...>
To: "AQ_NFS" <AQ_NFS@yahoogroups.com>
Sent: Thursday, February 28, 2013 7:27:57 PM
Subject: [AQ_NFS] Build 8

I just updated to to build 8. I was not having some of the issues posted on the
group. Now accessing familysearch is much, much, much slower. I constantly get
the message that familysearch is retrying when in ORTS or the synchronize
screen, then it says “cURL unable to connect AQ to FamilySearch, couldn’t
connect to host, Would you like to retry?” If I click “Retry” it often
goes and finds more information but very slowly. Is there anything I can do to
speed up the process?

Margaret

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



------------------------------------

Yahoo! Groups Links

I have updated build 8 and for the past 6 six hours have had the same issues
as Margaret  at first I just thought that family search was being slow.
Don't think that is the problem though.



Sherry



I just updated to to build 8. I was not having some of the issues posted on
the group. Now accessing familysearch is much, much, much slower. I
constantly get the message that familysearch is retrying when in ORTS or the
synchronize screen, then it says "cURL unable to connect AQ to FamilySearch,
couldn't connect to host, Would you like to retry?" If I click "Retry" it
often goes and finds more information but very slowly. Is there anything I
can do to speed up the process?



Margaret







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

All,

I haven't dont the update (yet), but earlier today, before Gaylon
announced build 8's availability, I was seeing the retry screen quite
often. I noticed that the FamilySearch site was also experiencing
problems when accessing it for searches and also working with people
in Family Tree.

So, not AQ, but FamilySearch . . . having a rough time of it. I also
noticed problems with Ancestry.com, possibly general internet problems
and not tied to either site.

Tom

All:

I wanted to make sure that you were all aware that AQ still helps you combine
records in FamilySearch.

At the request of FamilySearch, AQ no longer does an actual combine in NFS.
Rather, if you go through the same processes in AQ to either Link records, or
Search for Duplicates, and find duplicates in FamilySearch, you can still use
the "Combine" button. When you do, AQ will not actually do a Combine, but rather
it will bring up FamilySearch in your browser to the Merge screen, and will put
the IDs of the two records that you have identified as duplicates. You will
still have to complete the Merge process in Family Tree, but at least you were
able to use the tools in AQ to determine the duplicates.

Gaylon




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

Gordon....

All attempts to merge/combine records in AQ have resulted in errors
stating that they cannot be performed in Family Tree allthough I am
only accessing nFS.   So what's up?  --- Terry

On Sat, 2 Mar 2013 23:01:45 -0700 (MST), you wrote:

>All:
>
>I wanted to make sure that you were all aware that AQ still helps you combine
records in FamilySearch.
>
>At the request of FamilySearch, AQ no longer does an actual combine in NFS.
Rather, if you go through the same processes in AQ to either Link records, or
Search for Duplicates, and find duplicates in FamilySearch, you can still use
the "Combine" button. When you do, AQ will not actually do a Combine, but rather
it will bring up FamilySearch in your browser to the Merge screen, and will put
the IDs of the two records that you have identified as duplicates. You will
still have to complete the Merge process in Family Tree, but at least you were
able to use the tools in AQ to determine the duplicates.
>
>Gaylon
>
>
>
>
>[Non-text portions of this message have been removed]

I tried this this morning, and AQ closes and opens Family Tree, but it does
not put the ID's of the records, it leaves you on the main screen.



From: AQ_NFS@yahoogroups.com [mailto:AQ_NFS@yahoogroups.com] On Behalf Of
Gaylon Findlay
Sent: Saturday, March 02, 2013 11:02 PM
To: AQ NFS
Subject: [AQ_NFS] Merging in Family Tree with AQ





All:

I wanted to make sure that you were all aware that AQ still helps you
combine records in FamilySearch.

At the request of FamilySearch, AQ no longer does an actual combine in NFS.
Rather, if you go through the same processes in AQ to either Link records,
or Search for Duplicates, and find duplicates in FamilySearch, you can still
use the "Combine" button. When you do, AQ will not actually do a Combine,
but rather it will bring up FamilySearch in your browser to the Merge
screen, and will put the IDs of the two records that you have identified as
duplicates. You will still have to complete the Merge process in Family
Tree, but at least you were able to use the tools in AQ to determine the
duplicates.

Gaylon

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





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