Sure, I understand. No problem! I am pretty sure the problem is on the Quicken side, rather than AQbanking. Others who have reported these problems over the last year or so have also noted that their attempts to negotiate with their financial institutions have been met with resistance from the banks. The successes that have been reported have resulted from users who downloaded a recent copy of Quicken and sniffed the packets that come and go during a session with their bank under Quicken. I long ago abandoned downloading transactions from banks, for these reasons, but you could always try that approach.
David -------- Original Message -------- From: Elmar <etsc...@gmail.com> Sent: Sat Mar 13 11:04:12 EST 2021 To: gnucash-user@gnucash.org Cc: David H <hell...@gmail.com>, sunfis...@yahoo.com Subject: Re: [GNC] OFX connect/AQbanking problem Thank you for the explanation, David. My "pique" if you will, was the lack of response following the last reply. What I was hoping for was a pointer to what changed between version 2 and version 4 of GC in aqbanking, since the older version did downloads fine, but the new version doesn't, or failing that, some way to diagnose the problem based on the error message, or lastly a person I could contact that knows the internals of the module, especially since Quicken is supported by the bank (I don't have Quicken, btw). In any case, I don't "blame" anyone, especially not for a volunteer maintained and developed program. Such an attitude is imho simply wrong. I apologize if I came off too strong. - Elmar On 3/13/21 10:51 AM, gnucash-user-requ...@gnucash.org wrote: > Message: 12 > Date: Sat, 13 Mar 2021 10:51:39 -0500 > From: "D." <sunfis...@yahoo.com> > To: Elmar <etsc...@gmail.com> > Cc: David H <hell...@gmail.com>, Rainer Dorsch via gnucash-user > <gnucash-user@gnucash.org> > Subject: Re: [GNC] OFX connect/AQbanking problem. > Message-ID: <f80b6293-2ef7-4dde-bc07-5ba6711ca...@yahoo.com> > Content-Type: text/plain; charset=UTF-8 > > Elmar, > > The AQbanking connection is a commercially-maintained black box protocol that > was previously reverse engineered by the diligent volunteer maintainer of the > AQbanking package. The fact that it failed when the commercial vendor altered > the innards inside the box is not surprising. The ongoing challenges of > figuring out the workarounds demonstrates the skill with which that > commercial vendor has created their new system. There have been numerous > discussions on these lists regarding different attempts. That they haven't > worked for you is lamentable, to be sure, but not a reason to blame the group > for not providing you a solution. > > David T. > > > -------- Original Message -------- > From: Elmar <etsc...@gmail.com> > Sent: Sat Mar 13 09:33:50 EST 2021 > To: David H <hell...@gmail.com> > Cc: GNU Cash User <gnucash-user@gnucash.org> > Subject: Re: [GNC] OFX connect/AQbanking problem. > > Alas, it seems as if the assembled knowledge base cannot solve this.? It > bothers me that this used to work fine in the older version, but now > fails, despite having the bank in the database.? No help at all?? The > bank will not "expose" its OFX files for download - only CSV, and that's > a royal pain. - Elmar _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
