Re: [GNC] [GNC-dev] PDF Reports

[Michael Hendry]

> On 18 Mar 2020, at 03:00, David Carlson  wrote:
> 
> I added gnucash-user to the cc to distribute this to wider audience.
> 
> I believe that if you export to pdf, then some pdf readers do split between
> lines.  I think Firefox is one that works ok, but it has been a while since
> I tried it.
> 
> David Carlson

Morning, Alan and David.

I use GC 3.8 on iMac with High Sierra.

The annoyingly split lines in reports occur if I use the “Print” or “Make PDF” 
buttons.

It’s as though the page-breaking method is working in on rasters rather than 
lines of text, and I recall from previous complaints I’ve made about this that 
it’s ascribed to GTK.

The information is all there, but if you want a better-looking PDF you can use 
the “Export” button to save the report in HTML format, open the report in a 
browser (Safari in my case), and use the browser’s export-to-pdf function.

You’ll still get page-breaks within a multi-line transaction from time to time, 
but no line of text is split horizontally.

Michael

> 
> On Tue, Mar 17, 2020, 5:48 PM Alan Auerbach  wrote:
> 
>> I am a very new gnucash user and finding my way through the app. I am
>> finding it very easy to use and useful as a replacement for Quicken 2000. I
>> have one issue with the Reconciliation Report (I do not know if this issue
>> applies to other reports).
>> 
>> 
>> 
>> I selected the Technicolor report which looks great. However, when I print
>> it as a PDF or export it as a PDF, the page breaks can come in the middle
>> of
>> a text line with the upper parts of the characters on one page and the
>> lower
>> parts on the next page. Is there a setting that I can select to resolve
>> this
>> anomaly?
>> 
>> 
>> 
>> Best wishes,
>> /s/ Alan Auerbach
>> 14343 North Frank Lloyd Wright Boulevard, Apt. 1009
>> Scottsdale, AZ 85260-3634
>> (480) 657-7543 Home
>> (480) 922-0484 Text
>> (844) 395-7098 Fax
>> 
>> 
>> 
>> ___
>> gnucash-devel mailing list
>> gnucash-de...@gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>> 
> ___
> 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.



___
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.

Re: [GNC] AQBanking OFX DirectConnect

[csingley]

> Aside from the extra whitespace, which shouldn't matter, the git code has
closing tags on every element while the AQB5 code has closing tags only on
grouping elements.
> 
> USERID is specified in the OFX 1.6 DTD as
> 
> and according to
> https://en.wikipedia.org/wiki/Standard_Generalized_Markup_Language#OMITTAG
> the "- o" in the middle means that it should have an opening tag and no
> closing tag.

Sorry to butt in..  MAY have, not SHOULD have.  Closing tags are optional
for OFXv1 "elements" (i.e. data-bearing leaf nodes).

But the spec doesn't really matter in the real world.  The FIs code to
Quicken, not to the spec... and Quicken sends OFXv1 with unclosed elements. 
Therefore, AqBanking really should do so as well in order to be useful.

Contrary to the spec, USAA doesn't accept closing tags on elements. 
However, USAA does accept OFXv2, specifically versions 202 and 205.  Just
send them XML.

Here's the result of scanning USAA's server:

(ofxtools) 6:30:50 csingley@nous ofxtools sequences ? ofxget scan usaa
[{"versions": [102, 151], "formats": [{"pretty": false, "unclosedelements":
true}, {"pretty": true, "unclosedelements": true}]}, {"versions": [200,
202], "formats": [{"pretty": false}, {"pretty": true}]}, {"chgpinfirst":
false, "clientuidreq": false, "authtokenfirst": false, "mfachallengefirst":
false}]




--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
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.

Re: [GNC] General Ledger

[Michael or Penny Novack]

On 3/18/2020 1:59 AM, Adrian Yong wrote:

Thank you very much for your assistance.

I submit the following to the auditors:

1) P&L
2) Balance Sheet
3) Journal
4) General Ledger
5) Funds(Cash) Flow Statement
6) Trial Balance

That's because they don't use QuickBooks...

Regards,
Adrian

All of these are standard reports, just as they were in the old pen and 
ink on paper days.


Is your question how to produce each of these when using gnucash? Keep 
in mind that in some of these cases, terminology/names may be part of 
the issue. Thus "general ledger" can refer to both the ledger* itself 
and a report of it. At least part of the problem is the names used by 
gnucash.


Michael D Novack

* The "general" in the name is because of "cash book accounting", a 
shortcut method from the old days where the :cash" account was handled 
differently from the rest << since 90+% of transactions affected cash, 
those were not journalized but entered into the special "cash" ledger 
and posted from there --- actually similar to what we do in gnucash for 
all accounts --- think "virtual journal" bookkeeping >>


In traditional pen and ink on paper all transactions initially entered 
into the "journal" and then POSTED from there to the ledger. Errors 
while posting were frequent, finding them "fun". You can think of 
gnucash as backwards auto-posting. You enter directly into the ledger 
BUT gnucash can show you the corresponding "journal" if you ask it to.



___
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.

[GNC] configuring scroll bars

[mcmurchy1917techy via gnucash-user]

Hi everyone

My system is

   Slackware Current
   KDE5 Plasma

with

   gtk+3    3.24.14
   linux    5.4.25
   gnucash  3.8

I have a config file .config/gtk-3.0/gtk.css which contains the folllowing


@import 'colors.css';

scrollbar {
  -GtkScrollbar-has-backward-stepper: true;
  -GtkScrollbar-has-forward-stepper: true;
}

scrollbar, scrollbar button, scrollbar slider {
   min-width: 24px;
   min-height: 36px;


This gives me a wide vertical scroll bar with a block at each end where 
the up and down arrows for the scrollbar are supposed to go, under 
normal operation the blocks are blank/empty they don't contain the 
up/down arrows.


If I click the blocks at each end of the scroll bar they behave as 
scrolling up and down as would be expected.


If I open up a dialog like File->Properties the character < appears in 
the top block and the character > appears in the bottom block of the 
vertical scroll bar. When the dialog is closed these characters disappear.


So two questions

1. How do I get the correct characters to appear at each end of the
   scrollbar i.e. the upward pointing arrow and the downward pointing
   arrow?
2. How do I get these characters to display under normal operation i.e.
   other then when displaying a dialog box?

Thanks




___
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.

Re: [GNC] AQBanking OFX DirectConnect

[chris graves]

An additional bit of information from /tmp/ofx.log: 
AQB5:
Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318081757.000

...

git:
Sending:
-


...

> On Mar 17, 2020, at 10:40 AM, John Ralls  wrote:
> 
> 
> 
>> On Mar 17, 2020, at 9:45 AM, John Ralls  wrote:
>> 
>> 
>> 
>>> On Mar 15, 2020, at 1:21 PM, John Ralls  wrote:
>>> 
 
 On Mar 15, 2020, at 12:47 PM, Martin Preuss  wrote:
 
 Hi,
 
 Am 15.03.20 um 20:17 schrieb John Ralls:
> I just made a MacOS build with the latest AQBanking so I could test it 
> with my bank (USAA). No go, and a bit of troubleshooting reveals that 
> it's because AQBanking now uses the XML-based OFX V2. AFAIK that's not 
> supported by any US bank.
 [...]
 
 OFX2 is the only version I could get access to a test server for, so
 thats what I implemented so far.
 
 However, since the OFX spec state that banks should also accept XML like
 OFX requests (i.e. OFX files with closing XML elements) the code might
 be adjustable for this...
 
 I will try to add a mode in which the plugin sends the headers
 previously used for OFX1 and still send requests with closing XML
 elements, at least according to the specs I read that should work...
 
 Anyway, as I wrote before I can't test it myself. There is only person -
 so far - I heard of from the US who tested the latest code with a real
 server and I really appreciate his help, but he seems to be using the
 prebuilt Windows version which makes the debug process... well... 
 difficult.
 
 It would be extremely helpfull to have someone who could compile and
 test a version from GIT, but given the different timezones the possible
 OFX users and I live in that might be time consuming for both sides...
>>> 
>>> Martin,
>>> 
>>> As I said here and in my bug report, AQB 5's OFX backend works well and has 
>>> done for many years. If you just update it for the new AQB6 and Gwen5 API 
>>> it has a good chance of working.
>>> 
>>> I can build from git and test. So far there's no need for debugging, simply 
>>> comparing the OFX from 5.8 and 6.1 showed me the problem: OFX DirectConnect 
>>> servers using V1 can't parse the XML you send in the request and 400, see 
>>> the transcripts in the bug report.
>>> 
>>> The current OFX spec doesn't matter if the bank is using software written 
>>> for OFX V1 as nearly all in the US do.
>> 
>> Martin,
>> 
>> Frank noticed yesterday that you'd pushed a large OFX V1 change to AQBanking 
>> master, so I pulled it and tested it. Unfortunately its a total fail because 
>> the V1 code formats the OFX in XML.
>> 
>> V1 servers cannot parse XML and return a 400 error.
> 
> Martin,
> 
> Sorry, that's not quite right. It's not XML, but it does still 400. The 
> headers match those sent by AQB5, but the AQB5 request block is
> 
> 20200315112517XX
> X
> ENGUSAA24591QWIN2300202003151125171202003140020200315112517Y
> 
> unrolled and indented:
> 
>  
>
>  20200315112517
>  XX
>  X
>  ENG
>  
>USAA
>24591
>  
>  QWIN
>  2300
>
>  
>  
>
>  20200315112517
>  1
>  
>
>  
>
>
>  2020031400
>  20200315112517
>  Y
>
>  
>
>  
> 
> 
> 
> and git V1 sends
> 
> 
> 
> 20200317095100
> 
> 
> ENG
> 
> USAA
> 24591
> 
> QWIN
> 2300
> 
> 
> 
> 
> 20200317095103
> 
> 
> 24591
> 
> 
> 
> 2020031400
> 2020031700
> Y
> 
> 
> 
> 
> 
> 
> Aside from the extra whitespace, which shouldn't matter, the git code has 
> closing tags on every element while the AQB5 code has closing tags only on 
> grouping elements.
> 
> USERID is specified in the OFX 1.6 DTD as
> 
> and according to 
> https://en.wikipedia.org/wiki/Standard_Generalized_Markup_Language#OMITTAG 
> the "- o" in the middle means that it should have an opening tag and no 
> closing tag.
> 
> Regards,
> John Ralls
> 
> 
> 
> 
> 
> ___
> 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.

___
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

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

ofxtools -- nice toolset!

Here are the results from my bank:
ofxget scan kinecta
[{"versions": [102, 103], "formats": [{"pretty": false, "unclosedelements":
false}, {"pretty": false, "unclosedelements": true}, {"pretty": true,
"unclosedelements": false}, {"pretty": true, "unclosedelements": true}]},
{"versions": [], "formats": []}, {"chgpinfirst": false, "clientuidreq":
true, "authtokenfirst": false, "mfachallengefirst": false}]

On Wed, Mar 18, 2020 at 4:38 AM csingley  wrote:

> > Aside from the extra whitespace, which shouldn't matter, the git code has
> closing tags on every element while the AQB5 code has closing tags only on
> grouping elements.
> >
> > USERID is specified in the OFX 1.6 DTD as
> > 
> > and according to
> >
> https://en.wikipedia.org/wiki/Standard_Generalized_Markup_Language#OMITTAG
> > the "- o" in the middle means that it should have an opening tag and no
> > closing tag.
>
> Sorry to butt in..  MAY have, not SHOULD have.  Closing tags are optional
> for OFXv1 "elements" (i.e. data-bearing leaf nodes).
>
> But the spec doesn't really matter in the real world.  The FIs code to
> Quicken, not to the spec... and Quicken sends OFXv1 with unclosed
> elements.
> Therefore, AqBanking really should do so as well in order to be useful.
>
> Contrary to the spec, USAA doesn't accept closing tags on elements.
> However, USAA does accept OFXv2, specifically versions 202 and 205.  Just
> send them XML.
>
> Here's the result of scanning USAA's server:
>
> (ofxtools) 6:30:50 csingley@nous ofxtools sequences ? ofxget scan usaa
> [{"versions": [102, 151], "formats": [{"pretty": false, "unclosedelements":
> true}, {"pretty": true, "unclosedelements": true}]}, {"versions": [200,
> 202], "formats": [{"pretty": false}, {"pretty": true}]}, {"chgpinfirst":
> false, "clientuidreq": false, "authtokenfirst": false, "mfachallengefirst":
> false}]
>
>
>
>
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> 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.
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Christopher Singley]

Thanks.  Just, y'know, keep it cool on the profile scanning... each one 
spams a lot of requests.


Your bank's server has an OK parser... standards-compliant OFXv1.0.3 
(what Quicken sends).  Sadly no OFXv2 support.


On 3/18/20 10:50 AM, Chris Graves wrote:

ofxtools -- nice toolset!

Here are the results from my bank:
ofxget scan kinecta
[{"versions": [102, 103], "formats": [{"pretty": false, 
"unclosedelements": false}, {"pretty": false, "unclosedelements": 
true}, {"pretty": true, "unclosedelements": false}, {"pretty": true, 
"unclosedelements": true}]}, {"versions": [], "formats": []}, 
{"chgpinfirst": false, "clientuidreq": true, "authtokenfirst": false, 
"mfachallengefirst": false}]


On Wed, Mar 18, 2020 at 4:38 AM csingley > wrote:


> Aside from the extra whitespace, which shouldn't matter, the git
code has
closing tags on every element while the AQB5 code has closing tags
only on
grouping elements.
>
> USERID is specified in the OFX 1.6 DTD as
> 
> and according to
>
https://en.wikipedia.org/wiki/Standard_Generalized_Markup_Language#OMITTAG
> the "- o" in the middle means that it should have an opening tag
and no
> closing tag.

Sorry to butt in..  MAY have, not SHOULD have.  Closing tags are
optional
for OFXv1 "elements" (i.e. data-bearing leaf nodes).

But the spec doesn't really matter in the real world.  The FIs code to
Quicken, not to the spec... and Quicken sends OFXv1 with unclosed
elements.
Therefore, AqBanking really should do so as well in order to be
useful.

Contrary to the spec, USAA doesn't accept closing tags on elements.
However, USAA does accept OFXv2, specifically versions 202 and
205.  Just
send them XML.

Here's the result of scanning USAA's server:

(ofxtools) 6:30:50 csingley@nous ofxtools sequences ? ofxget scan usaa
[{"versions": [102, 151], "formats": [{"pretty": false,
"unclosedelements":
true}, {"pretty": true, "unclosedelements": true}]}, {"versions":
[200,
202], "formats": [{"pretty": false}, {"pretty": true}]},
{"chgpinfirst":
false, "clientuidreq": false, "authtokenfirst": false,
"mfachallengefirst":
false}]




--
Sent from:
http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
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.


___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

Interesting. USAA can't parse the OFXv2 that AQBanking 6.1.2 emits. 
Unfortunately it just returns an HTTP 400 response, no details. Perhaps like v1 
there are Intuit-induced quirks in the v2 parser as well and we'd need to 
capture a v2 interaction with Quicken to figure them out.

Regards,
John Ralls

> On Mar 18, 2020, at 4:35 AM, csingley  wrote:
> 
>> Aside from the extra whitespace, which shouldn't matter, the git code has
> closing tags on every element while the AQB5 code has closing tags only on
> grouping elements.
>> 
>> USERID is specified in the OFX 1.6 DTD as
>> 
>> and according to
>> https://en.wikipedia.org/wiki/Standard_Generalized_Markup_Language#OMITTAG
>> the "- o" in the middle means that it should have an opening tag and no
>> closing tag.
> 
> Sorry to butt in..  MAY have, not SHOULD have.  Closing tags are optional
> for OFXv1 "elements" (i.e. data-bearing leaf nodes).
> 
> But the spec doesn't really matter in the real world.  The FIs code to
> Quicken, not to the spec... and Quicken sends OFXv1 with unclosed elements. 
> Therefore, AqBanking really should do so as well in order to be useful.
> 
> Contrary to the spec, USAA doesn't accept closing tags on elements. 
> However, USAA does accept OFXv2, specifically versions 202 and 205.  Just
> send them XML.
> 
> Here's the result of scanning USAA's server:
> 
> (ofxtools) 6:30:50 csingley@nous ofxtools sequences ? ofxget scan usaa
> [{"versions": [102, 151], "formats": [{"pretty": false, "unclosedelements":
> true}, {"pretty": true, "unclosedelements": true}]}, {"versions": [200,
> 202], "formats": [{"pretty": false}, {"pretty": true}]}, {"chgpinfirst":
> false, "clientuidreq": false, "authtokenfirst": false, "mfachallengefirst":
> false}]
> 
> 
> 
> 
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> 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.

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Christopher Singley]

You're sending VERSION="220", which USAA doesn't accept.  You need to 
send VERSION="200" or VERSION="202".  Try that.


On 3/18/20 11:31 AM, John Ralls wrote:

Interesting. USAA can't parse the OFXv2 that AQBanking 6.1.2 emits. 
Unfortunately it just returns an HTTP 400 response, no details. Perhaps like v1 
there are Intuit-induced quirks in the v2 parser as well and we'd need to 
capture a v2 interaction with Quicken to figure them out.

Regards,
John Ralls


On Mar 18, 2020, at 4:35 AM, csingley  wrote:


Aside from the extra whitespace, which shouldn't matter, the git code has

closing tags on every element while the AQB5 code has closing tags only on
grouping elements.

USERID is specified in the OFX 1.6 DTD as

and according to
https://en.wikipedia.org/wiki/Standard_Generalized_Markup_Language#OMITTAG
the "- o" in the middle means that it should have an opening tag and no
closing tag.

Sorry to butt in..  MAY have, not SHOULD have.  Closing tags are optional
for OFXv1 "elements" (i.e. data-bearing leaf nodes).

But the spec doesn't really matter in the real world.  The FIs code to
Quicken, not to the spec... and Quicken sends OFXv1 with unclosed elements.
Therefore, AqBanking really should do so as well in order to be useful.

Contrary to the spec, USAA doesn't accept closing tags on elements.
However, USAA does accept OFXv2, specifically versions 202 and 205.  Just
send them XML.

Here's the result of scanning USAA's server:

(ofxtools) 6:30:50 csingley@nous ofxtools sequences ? ofxget scan usaa
[{"versions": [102, 151], "formats": [{"pretty": false, "unclosedelements":
true}, {"pretty": true, "unclosedelements": true}]}, {"versions": [200,
202], "formats": [{"pretty": false}, {"pretty": true}]}, {"chgpinfirst":
false, "clientuidreq": false, "authtokenfirst": false, "mfachallengefirst":
false}]




--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
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.

___
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.

Re: [GNC] General Ledger

[Adrien Monteleone]

#1, 2, are available in GnuCash and easy enough to produce.

#3 would be done as an ‘Account Report’ while viewing the General Journal. 
Recall though that you’ll have to adjust the View > Filter By to show the 
desired dates before running the report.

#4 can be accomplished as I previously noted with a Transaction Report. But as 
Michael pointed out, because the way GnuCash works, there won’t be any 
difference (other than maybe form) as to what #3 and #4 contain. As the Journal 
and Ledger are not separate things (you don’t make an entry and then transfer 
info) there won’t be any difference in the transaction info for each. You might 
have to produce each just to make the auditors happy till they learn one is 
pointless with GnuCash.

While #5 exists in GnuCash, it does not match any textbook example I’ve seen of 
such a report. If you can provide an obfuscated previous example we can advise 
if the built-in report will suffice or if you’d have to use some other report, 
or need something entirely custom.

#6 is available in GnuCash.

Also, note that GnuCash can export your data in CSV, and it is stored by 
default in XML, both of which are open formats (non-proprietary) and can 
possibly be imported by whatever software they use. (the XML is compressed by 
default, but you can set a preference to store it uncompressed, or just unzip 
it before sending) That might be an option. But the reports are certainly 
doable.

Regards,
Adrien

> On Mar 18, 2020 w12d78, at 12:59 AM, Adrian Yong 
>  wrote:
> 
> Thank you very much for your assistance.
> 
> I submit the following to the auditors:
> 
> 1) P&L
> 2) Balance Sheet
> 3) Journal
> 4) General Ledger
> 5) Funds(Cash) Flow Statement
> 6) Trial Balance
> 
> That's because they don't use QuickBooks...
> 
> Regards,
> Adrian


___
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.

[GNC] European electronic invoicing standard

[Michael L. Wilson]

Greetings,

Might someone be able to confirm whether GnuCash is able to issue
invoices in line with the European electronic invoicing standard?

https://ec.europa.eu/growth/single-market/public-procurement/digital/einvoicing_en

If any documentation exists concerning this, it would be greatly
appreciated.

Michael

___
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.

Re: [GNC] configuring scroll bars

[Adrien Monteleone]

Sounds like a Plasma preference, though I find it curious it is visible on 
dialogs but not the main window.

The proper solution probably involves resolving a display problem with GTK on 
Plasma, but you might be able to fake it with the `::before` pseudo element and 
some creative positioning to make it appear to float overlaid on the button. 
That might only work though if you can target each button independently.

Regards,
Adrien



> On Mar 18, 2020 w12d78, at 9:21 AM, mcmurchy1917techy via gnucash-user 
>  wrote:
> 
> Hi everyone
> 
> My system is
> 
>   Slackware Current
>   KDE5 Plasma
> 
> with
> 
>   gtk+33.24.14
>   linux5.4.25
>   gnucash  3.8
> 
> I have a config file .config/gtk-3.0/gtk.css which contains the folllowing
> 
>> @import 'colors.css';
>> 
>> scrollbar {
>>   -GtkScrollbar-has-backward-stepper: true;
>>   -GtkScrollbar-has-forward-stepper: true;
>> }
>> 
>> scrollbar, scrollbar button, scrollbar slider {
>>min-width: 24px;
>>min-height: 36px;
> 
> This gives me a wide vertical scroll bar with a block at each end where the 
> up and down arrows for the scrollbar are supposed to go, under normal 
> operation the blocks are blank/empty they don't contain the up/down arrows.
> 
> If I click the blocks at each end of the scroll bar they behave as scrolling 
> up and down as would be expected.
> 
> If I open up a dialog like File->Properties the character < appears in the 
> top block and the character > appears in the bottom block of the vertical 
> scroll bar. When the dialog is closed these characters disappear.
> 
> So two questions
> 
> 1. How do I get the correct characters to appear at each end of the
>   scrollbar i.e. the upward pointing arrow and the downward pointing
>   arrow?
> 2. How do I get these characters to display under normal operation i.e.
>   other then when displaying a dialog box?
> 
> Thanks

___
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.

Re: [GNC] configuring scroll bars

[Adrien Monteleone]

Is your main window set to full screen?

If so, do the buttons appear properly when you take it off full screen?

A quick work around might be to size the window to fill the screen but not use 
the full-screen setting. Then you know where to look for a setting or report a 
bug to either GTK or Plasma.

Do your QT apps behave the same way?

Regards,
Adrien

> On Mar 18, 2020 w12d78, at 9:21 AM, mcmurchy1917techy via gnucash-user 
>  wrote:
> 
> Hi everyone
> 
> My system is
> 
>   Slackware Current
>   KDE5 Plasma
> 
> with
> 
>   gtk+33.24.14
>   linux5.4.25
>   gnucash  3.8
> 
> I have a config file .config/gtk-3.0/gtk.css which contains the folllowing
> 
>> @import 'colors.css';
>> 
>> scrollbar {
>>   -GtkScrollbar-has-backward-stepper: true;
>>   -GtkScrollbar-has-forward-stepper: true;
>> }
>> 
>> scrollbar, scrollbar button, scrollbar slider {
>>min-width: 24px;
>>min-height: 36px;
> 
> This gives me a wide vertical scroll bar with a block at each end where the 
> up and down arrows for the scrollbar are supposed to go, under normal 
> operation the blocks are blank/empty they don't contain the up/down arrows.
> 
> If I click the blocks at each end of the scroll bar they behave as scrolling 
> up and down as would be expected.
> 
> If I open up a dialog like File->Properties the character < appears in the 
> top block and the character > appears in the bottom block of the vertical 
> scroll bar. When the dialog is closed these characters disappear.
> 
> So two questions
> 
> 1. How do I get the correct characters to appear at each end of the
>   scrollbar i.e. the upward pointing arrow and the downward pointing
>   arrow?
> 2. How do I get these characters to display under normal operation i.e.
>   other then when displaying a dialog box?
> 
> Thanks

___
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.

Re: [GNC] European electronic invoicing standard

[Adrien Monteleone]

I don’t see anything there about actual requirements. It appears to be just 
about the process of coming up with a standard. I did look over the ‘directive’ 
and still it was short on final specs.

Do you have a link for whatever was eventually settled on?

Regards,
Adrien

> On Mar 18, 2020 w12d78, at 11:37 AM, Michael L. Wilson 
>  wrote:
> 
> Greetings,
> 
> Might someone be able to confirm whether GnuCash is able to issue
> invoices in line with the European electronic invoicing standard?
> 
> https://ec.europa.eu/growth/single-market/public-procurement/digital/einvoicing_en
> 
> If any documentation exists concerning this, it would be greatly
> appreciated.
> 
> Michael

___
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.

Re: [GNC] European electronic invoicing standard

[Michael L. Wilson]

Hello!

I think the following might be useful:

https://docs.microsoft.com/en-us/dynamics365/finance/localizations/emea-oioubl-standards-electronic-invoicing

M

On 3/18/20 6:55 PM, Adrien Monteleone wrote:
> I don’t see anything there about actual requirements. It appears to be just 
> about the process of coming up with a standard. I did look over the 
> ‘directive’ and still it was short on final specs.
> 
> Do you have a link for whatever was eventually settled on?
> 
> Regards,
> Adrien
> 
>> On Mar 18, 2020 w12d78, at 11:37 AM, Michael L. Wilson 
>>  wrote:
>>
>> Greetings,
>>
>> Might someone be able to confirm whether GnuCash is able to issue
>> invoices in line with the European electronic invoicing standard?
>>
>> https://ec.europa.eu/growth/single-market/public-procurement/digital/einvoicing_en
>>
>> If any documentation exists concerning this, it would be greatly
>> appreciated.
>>
>> Michael
> 
> ___
> 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.
> 
___
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.

Re: [GNC] configuring scroll bars

[mcmurchy1917techy via gnucash-user]

Apologies, might not have explained it very well.

The arrows < > do appear on the vertical scrollbar of the main window, 
but only when a dialog has the main focus. When the dialog is closed the 
arrows disappear and will only reappear if another dialog is opened.


Your "proper solution" is probably way beyond my capability. I'll give 
it some thought though.


Thanks

Alex

On 18/03/2020 16:45, Adrien Monteleone wrote:

Sounds like a Plasma preference, though I find it curious it is visible on 
dialogs but not the main window.

The proper solution probably involves resolving a display problem with GTK on 
Plasma, but you might be able to fake it with the `::before` pseudo element and 
some creative positioning to make it appear to float overlaid on the button. 
That might only work though if you can target each button independently.

Regards,
Adrien




On Mar 18, 2020 w12d78, at 9:21 AM, mcmurchy1917techy via gnucash-user 
 wrote:

Hi everyone

My system is

   Slackware Current
   KDE5 Plasma

with

   gtk+33.24.14
   linux5.4.25
   gnucash  3.8

I have a config file .config/gtk-3.0/gtk.css which contains the folllowing


@import 'colors.css';

scrollbar {
   -GtkScrollbar-has-backward-stepper: true;
   -GtkScrollbar-has-forward-stepper: true;
}

scrollbar, scrollbar button, scrollbar slider {
min-width: 24px;
min-height: 36px;

This gives me a wide vertical scroll bar with a block at each end where the up 
and down arrows for the scrollbar are supposed to go, under normal operation 
the blocks are blank/empty they don't contain the up/down arrows.

If I click the blocks at each end of the scroll bar they behave as scrolling up 
and down as would be expected.

If I open up a dialog like File->Properties the character < appears in the top 
block and the character > appears in the bottom block of the vertical scroll bar. 
When the dialog is closed these characters disappear.

So two questions

1. How do I get the correct characters to appear at each end of the
   scrollbar i.e. the upward pointing arrow and the downward pointing
   arrow?
2. How do I get these characters to display under normal operation i.e.
   other then when displaying a dialog box?

Thanks

___
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.

___
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.

Re: [GNC] [GNC-dev] Online Access to Bank of America

[Alan Auerbach]

Dear John,

I am using Win10 Pro. If I go back to gnucash 3.6, will I lose valuable
updates in exchange for OFX Direct Connect? It seems to be a choice or wait
and see if it is working in the next update.

Best wishes,
/s/ Alan 
14343 North Frank Lloyd Wright Boulevard, Apt. 1009 
Scottsdale, AZ 85260-3634 
(480) 657-7543 Home 
(480) 922-0484 Text 
(844) 395-7098 Fax

-Original Message-
From: John Ralls  
Sent: Tuesday, March 17, 2020 8:05 PM
To: aauerb...@poolthing.com
Cc: Gnucash Users 
Subject: Re: [GNC-dev] Online Access to Bank of America



> On Mar 17, 2020, at 5:19 PM, Alan Auerbach 
wrote:
> 
> Dear John,
> 
> Thank you for getting back to me so quickly. I apologize for being in 
> the wrong place. I thought that gnucash-user is for accounting 
> questions rather than technical issues.
> 
> Thank you for referring me to
> https://wiki.gnucash.org/wiki/Setting_up_OFXDirectConnect and 
> http://ofxhome.com/. I had read the wiki before and during my attempt 
> to get OFX Direct Connect working. Ofxhome.com is where I found the proper
codes.
> 
> I have since heard from Chris Graves who told me that OFX Direct 
> Connect access is broken in the 3.8 version of gnucash that I am 
> using. That would be too bad.
> 
> Best wishes,
> /s/ Alan
> 
> -Original Message-
> From: John Ralls 
> Sent: Tuesday, March 17, 2020 3:54 PM
> To: aauerb...@poolthing.com
> Cc: gnucash-user 
> Subject: Re: [GNC-dev] Online Access to Bank of America
> 
> 
> 
>> On Mar 17, 2020, at 3:31 PM, Alan Auerbach 
> wrote:
>> 
>> As a brand-new user, I am trying to setup online access to my Bank of 
>> America account. I have entered the requested information including 
>> correct URL (from the gnucash table), the routing number and SWIFT 
>> code. After that point, I cannot get further. The next button remains 
>> grayed out. What am I missing?
>> 
> 
> As a brand-new user you're first of missing that gnucash-devel (this 
> list) is for developers to discuss GnuCash internals. Users should 
> subscribe to gnucash-user. For your convenience I've copied that list on
this reply.
> 
> The most likely answer to your question is that you haven't completed 
> all of the steps in the AQBanking Setup Wizard so that there are no 
> accounts set up. Some references:
> https://wiki.gnucash.org/wiki/Setting_up_OFXDirectConnect for 
> instructions on setting up.
> http://ofxhome.com/ for the best information on bank parameters. This 
> is the website that feeds the setup selection in the AQBanking Setup 
> Wizard and it tests them daily. It's worthwhile to check the setup 
> that you intend to use and make sure that it's still working: About 1/3 of
them don't any more.
> 
> Regards,
> John Ralls
> 
> 

Please remember to copy the list on all replies.

What version of GnuCash will work with OFX depends on what OS you're using.
It's true that with the Windows and MacOS bundles 3.8 won't work, but if
you've installed 3.8 on Linux it will depend upon what version of AQBanking
the distribution that you use provides.

In the case of MacOS and Windows you can pretty simply install an older
version (3.7 for MacOS, 3.6 for Windows) from our SourceForge or Github
sites.

Regards,
John Ralls



___
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.

Re: [GNC] European electronic invoicing standard

[Adrien Monteleone]

Okay, that looks like the basic requirement is an XML document that conforms to 
UBL (Universal Business Language) with some country specific additional 
requirements. (those would have to be investigated and addressed individually)

GnuCash doesn’t provide this out of the box, but it might be possible to obtain.

First, the default file format for GnuCash is compressed XML. You can opt to 
store it uncompressed, or uncompress it on demand. (unzip works fine)

You might then write a script to extract the invoice detail, as-is, then you’d 
need to see if it conforms to UBL. (and then the country requirements) It 
probably won’t, but perhaps some of those difference are just naming/tag 
conventions, so you might be able to script that as a translation. (GnuCash 
might label an invoice total with a different word than UBL, so you’d just do a 
find/replace on that string when contained as a tag)

I can’t say what might achieve the country specific requirements without seeing 
them. (that’s a bridge to cross later, and might not be so terrible)

Another option is to run the invoice report, export or copy/paste it to a text 
file. It is HTML. You should be able to find HTML > XML converters, and maybe 
even an HTML > UBL converter online. Then further massage from there.

A third option is to find some online service that will take XML or HTML and 
generate the proper file meeting whatever regulations you need.

On a side note, filing a bug/enhancement for GnuCash’s XML invoice storage to 
more closely conform to UBL might be beneficial to a large audience. It might 
make the better export format instead of HTML. (or in addition to)

Regards,
Adrien


> On Mar 18, 2020 w12d78, at 12:00 PM, Michael L. Wilson 
>  wrote:
> 
> Hello!
> 
> I think the following might be useful:
> 
> https://docs.microsoft.com/en-us/dynamics365/finance/localizations/emea-oioubl-standards-electronic-invoicing
> 
> M
> 
> On 3/18/20 6:55 PM, Adrien Monteleone wrote:
>> I don’t see anything there about actual requirements. It appears to be just 
>> about the process of coming up with a standard. I did look over the 
>> ‘directive’ and still it was short on final specs.
>> 
>> Do you have a link for whatever was eventually settled on?
>> 
>> Regards,
>> Adrien
>> 
>>> On Mar 18, 2020 w12d78, at 11:37 AM, Michael L. Wilson 
>>>  wrote:
>>> 
>>> Greetings,
>>> 
>>> Might someone be able to confirm whether GnuCash is able to issue
>>> invoices in line with the European electronic invoicing standard?
>>> 
>>> https://ec.europa.eu/growth/single-market/public-procurement/digital/einvoicing_en
>>> 
>>> If any documentation exists concerning this, it would be greatly
>>> appreciated.
>>> 
>>> Michael
>> 
>> ___
>> 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.
>> 
> 


___
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.

Re: [GNC] configuring scroll bars

[Adrien Monteleone]

Again, sounds like a preference in Plasma, though perhaps a design choice of 
Plasma, or even GTK.

I’m surprised you still have the scroll bar at all if that window doesn’t have 
focus.

There may not be an easy solution if that behavior is by design without an 
exposed preference to change it.

Regards,
Adrien

> On Mar 18, 2020 w12d78, at 12:12 PM, mcmurchy1917techy via gnucash-user 
>  wrote:
> 
> Apologies, might not have explained it very well.
> 
> The arrows < > do appear on the vertical scrollbar of the main window, but 
> only when a dialog has the main focus. When the dialog is closed the arrows 
> disappear and will only reappear if another dialog is opened.
> 
> Your "proper solution" is probably way beyond my capability. I'll give it 
> some thought though.
> 
> Thanks
> 
> Alex

___
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.

Re: [GNC] configuring scroll bars

[mcmurchy1917techy via gnucash-user]

The full screen / off full screen makes no difference. The character in 
the scroll bar up/down buttons is missing.


So far I've now looked at three GTK3 based applications - gnucash, 
libreoffice and firefox.


For all three applications, I can alter the width of the scrollbar by 
editing the appropriate settings in the file .config/gtk-3.0/gtk.css


 * gnucash under normal circumstances doesn't have the up/down
   character in the button at either end of the scrollbar. When a
   dialog is started a character does appear in the up/down buttons of
   the scrollbar, but incorrectly it contains left/right chevrons in
   the buttons.
 * libreoffice doesn't have any up/down character in the button at
   either end of the scrollbar, even if i start one of its dialogs.
 * firefox does have the correct up/down characters in the button at
   either end of the scrollbar.

firefox is interesting  in that it appears to be behaving correctly, so 
it might give me a handle on what the problem is.


Alex

On 18/03/2020 16:47, Adrien Monteleone wrote:

Is your main window set to full screen?

If so, do the buttons appear properly when you take it off full screen?

A quick work around might be to size the window to fill the screen but not use 
the full-screen setting. Then you know where to look for a setting or report a 
bug to either GTK or Plasma.

Do your QT apps behave the same way?

Regards,
Adrien


On Mar 18, 2020 w12d78, at 9:21 AM, mcmurchy1917techy via gnucash-user 
 wrote:

Hi everyone

My system is

   Slackware Current
   KDE5 Plasma

with

   gtk+33.24.14
   linux5.4.25
   gnucash  3.8

I have a config file .config/gtk-3.0/gtk.css which contains the folllowing


@import 'colors.css';

scrollbar {
   -GtkScrollbar-has-backward-stepper: true;
   -GtkScrollbar-has-forward-stepper: true;
}

scrollbar, scrollbar button, scrollbar slider {
min-width: 24px;
min-height: 36px;

This gives me a wide vertical scroll bar with a block at each end where the up 
and down arrows for the scrollbar are supposed to go, under normal operation 
the blocks are blank/empty they don't contain the up/down arrows.

If I click the blocks at each end of the scroll bar they behave as scrolling up 
and down as would be expected.

If I open up a dialog like File->Properties the character < appears in the top 
block and the character > appears in the bottom block of the vertical scroll bar. 
When the dialog is closed these characters disappear.

So two questions

1. How do I get the correct characters to appear at each end of the
   scrollbar i.e. the upward pointing arrow and the downward pointing
   arrow?
2. How do I get these characters to display under normal operation i.e.
   other then when displaying a dialog box?

Thanks

___
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.

___
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.

Re: [GNC] configuring scroll bars

[Adrien Monteleone]

Sorry, I sent too fast and read too slowly.

If the arrows only appear on the main window when a dialog has focus, but not 
when the main window has focus, that would seem backwards to me.

You might have a bug there. (which might still be part of a GTK on Plasma 
conflict)

Regards,
Adrien

> On Mar 18, 2020 w12d78, at 12:33 PM, Adrien Monteleone 
>  wrote:
> 
> Again, sounds like a preference in Plasma, though perhaps a design choice of 
> Plasma, or even GTK.
> 
> I’m surprised you still have the scroll bar at all if that window doesn’t 
> have focus.
> 
> There may not be an easy solution if that behavior is by design without an 
> exposed preference to change it.
> 
> Regards,
> Adrien
> 
>> On Mar 18, 2020 w12d78, at 12:12 PM, mcmurchy1917techy via gnucash-user 
>>  wrote:
>> 
>> Apologies, might not have explained it very well.
>> 
>> The arrows < > do appear on the vertical scrollbar of the main window, but 
>> only when a dialog has the main focus. When the dialog is closed the arrows 
>> disappear and will only reappear if another dialog is opened.
>> 
>> Your "proper solution" is probably way beyond my capability. I'll give it 
>> some thought though.
>> 
>> Thanks
>> 
>> Alex


___
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.

Re: [GNC] configuring scroll bars

[Adrien Monteleone]

I didn’t think either Firefox or LibreOffice were GTK. I thought each had its 
own toolkit.

GIMP is GTK (it was originally the GIMP Tool Kit) as is Gedit. (among others 
belonging to the Gnome desktop suite) Maybe try installing something like those 
and seeing what the scrollbars do.

Regards,
Adrien

> On Mar 18, 2020 w12d78, at 12:33 PM, mcmurchy1917techy via gnucash-user 
>  wrote:
> 
> The full screen / off full screen makes no difference. The character in the 
> scroll bar up/down buttons is missing.
> 
> So far I've now looked at three GTK3 based applications - gnucash, 
> libreoffice and firefox.
> 
> For all three applications, I can alter the width of the scrollbar by editing 
> the appropriate settings in the file .config/gtk-3.0/gtk.css
> 
> * gnucash under normal circumstances doesn't have the up/down
>   character in the button at either end of the scrollbar. When a
>   dialog is started a character does appear in the up/down buttons of
>   the scrollbar, but incorrectly it contains left/right chevrons in
>   the buttons.
> * libreoffice doesn't have any up/down character in the button at
>   either end of the scrollbar, even if i start one of its dialogs.
> * firefox does have the correct up/down characters in the button at
>   either end of the scrollbar.
> 
> firefox is interesting  in that it appears to be behaving correctly, so it 
> might give me a handle on what the problem is.
> 
> Alex

___
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.

Re: [GNC] General Ledger

[Stephen M. Butler]

On 3/17/20 8:50 PM, Adrian Yong wrote:
> Hi Adrien,
>
> Thanks for your very detailed explanation...
>
> I appreciate that we enter each transaction using the double entry system
> into the accounts.. This is almost the same as manual accounting.
>
> The problem arises when the auditors do not use Gnucash. In the manual
> system, the auditors will be provided with a General Ledger which is a
> collation of all transactions sorted into each of the accounts.
>
> If the auditors uses Gnucash, all I need to do is to furnish them with
> gnucash data file and my problem would vanish... But
>
> Regards,
> Adrian

Adrian,

I give my CPA three items:

1.  Balance Sheet.

2.  Profit Loss statement

3.  Transaction Report of all transactions for the year sorted by
account and then by date within account.

So far he hasn't complained.

--Steve

>
>
>
>
> On Wed, 18 Mar. 2020, 01:28 Adrien Monteleone, <
> adrien.montele...@lusfiber.net> wrote:
>
>> I think I understand now what you are asking.
>>
>> TLDR; your GnuCash file **is** the General Ledger. GnuCash **is not**
>> QuickBooks. QuickBooks has a separate view of the General Ledger because
>> they otherwise hide it from you.
>>
>>
>> QuickBooks in particular, hides the double-entry nature of accounting from
>> you with their home screen. They strongly urge you to enter transactions
>> via the various flow steps that they provide and they really want you to
>> use their workflow. You don’t make entries in the General Ledger, but in
>> various special entry screens. But you can make direct General Ledger
>> entries for special cases. However, they frown upon it. You can also view
>> the General Ledger separately. (but you don’t have to in order to run a P&L
>> or Balance Sheet, but that is where all QuickBooks transactions are
>> officially stored.)
>>
>> GnuCash takes the opposite approach and offers double-entry, by default.
>> You don’t need to open something special, or run a special report, you
>> *are* working directly in the various accounts that are part of the General
>> Ledger. Thus, each GnuCash file *is* the General Ledger. It is the
>> collection of all of your accounts and all transactions in them, in one
>> place. There is a summary tab labeled “Accounts” where you can see balances
>> in any account at a glance without having to open each one or run a special
>> report. There is also a General Journal, which is the pen and paper
>> equivalent of putting all transactions in one place, then later copying
>> them to the individual accounts. (but with GnuCash you don’t have to copy
>> them, you just enter them once.) Think of the various account registers as
>> subsets of the General Journal. Some (like myself) prefer to work directly
>> in various accounts. Some prefer to enter transactions into the General
>> Journal.
>>
>> An exception to this direct entry approach is the Business Features. While
>> you don’t need to use them, you can, and they offer special functions and
>> reports. If you use them, you should only make changes (with regards to
>> those individual special business transactions) via their special windows
>> rather than directly in the AR/AP accounts. But you can always view AR/AP
>> at any time. You can also have ‘Other’ AR/AP accounts and make all the
>> manual entries in them that you need. With regard to Bills and Invoices,
>> you can do those manually, or you can use the Business Features. If you do
>> so, you can’t edit the resulting transactions in Expense or Income accounts
>> directly, you have to use the Edit Bill/Invoice window to do so. (but you
>> can always view those transactions at any time, just like AR/AP by simply
>> viewing the relevant Income or Expense account, they are in fact, the same
>> transactions as what appears in AR/AP.)
>>
>>
>> Regards,
>> Adrien
>>
>>
>>
>>
>>> On Mar 17, 2020 w12d77, at 2:20 AM, Adrian Yong <
>> adrianyong.88p...@gmail.com> wrote:
>>>
>>> Adrien,
>>>
>>> In the General Ledger, every account has it history recorded and all
>> these is collated in one book called the General Ledger...
>>> As I am used to QuickBooks and manually accounting methods, the General
>> Ledger is the basis for P&L, and Balance Sheet. QuickBooks seems to emulate
>> manual accounting.
>>> Somehow, I have to generate a report on each account and collate them
>> manually into one collection..
>>> Regards,
>>> Adrian
>>>
>>> On Tue, 17 Mar. 2020, 13:39 Adrien Monteleone, <
>> adrien.montele...@lusfiber.net> wrote:
>>> If you mean you want to see the individual transaction activity in your
>> accounts related to a single customer, yes.
>>> If you just want to see the balanced owed by all customers, you can use
>> the Accounts Receivable report. (each customer can be listed separately,
>> along with a total)
>>> But both of these are entirely different things than your original
>> question. Which is quite fine, but please do clarify what it is you are
>> trying to accomplish so we can help you efficiently.
>>> Regard

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

> On Mar 18, 2020, at 9:33 AM, Christopher Singley  wrote:
> 
> You're sending VERSION="220", which USAA doesn't accept.  You need to send 
> VERSION="200" or VERSION="202".  Try that.

No joy, I still get a 400 response, but it does occur to me that it isn't 
necessarily an OFX issue, it could be that the HTTP request itself is malformed.






20200318122832


ENG

USAA
24591

QWIN
2300




20200318122835


24591
XX


2020031000
2020031800
Y






Regards,
John Ralls
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[chris graves]

I was thinking that it could be the first two lines of your file below.

> On Mar 18, 2020, at 12:40 PM, John Ralls  wrote:
> 
> 
> 
>> On Mar 18, 2020, at 9:33 AM, Christopher Singley  wrote:
>> 
>> You're sending VERSION="220", which USAA doesn't accept.  You need to send 
>> VERSION="200" or VERSION="202".  Try that.
> 
> No joy, I still get a 400 response, but it does occur to me that it isn't 
> necessarily an OFX issue, it could be that the HTTP request itself is 
> malformed.
> 
> 
> 
> 
> 
> 
> 20200318122832
> 
> 
> ENG
> 
> USAA
> 24591
> 
> QWIN
> 2300
> 
> 
> 
> 
> 20200318122835
> 
> 
> 24591
> XX
> 
> 
> 2020031000
> 2020031800
> Y
> 
> 
> 
> 
> 
> 
> Regards,
> John Ralls
> ___
> 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.

___
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.

Re: [GNC] [GNC-dev] Online Access to Bank of America

[John Ralls]

> On Mar 18, 2020, at 10:18 AM, Alan Auerbach  wrote:
> 
> Dear John,
> 
> I am using Win10 Pro. If I go back to gnucash 3.6, will I lose valuable
> updates in exchange for OFX Direct Connect? It seems to be a choice or wait
> and see if it is working in the next update.

Depends. If you're in the habit of keeping several graph reports open then you 
should go to 3.5, there was a webkit build problem in 3.6 and 3.7 that caused 
GnuCash to hang with that. There have been some new reports and some bug fixes, 
none of which I would consider deal-breaking but you can review the release 
notes at https://www.gnucash.org/news.phtml and decide for yourself.

Regards,
John Ralls

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Christopher Singley]

Are you able to make OFX connection with USAA's server in any manner 
whatsoever?


I have a dormant USAA bank account that I used to be able to download, 
that now is returning HTTP 400 for the same OFX configs that used to 
work.  They haven't moved the server, have they?


(ofxtools) 11:39:27 csingley@nous ofxtools sequences ? ofxget list usaa

USAA Federal Savings Bank
ofxhome = 483
url = https://service2.usaa.com/ofx/OFXServlet
version = 103
org = USAA
fid = 24591
user = 
bankid = 314074269
savings = 
checking = 
unclosedelements = true
clientuid = 

These used to work, but now raise HTTP 400.

The problem may be larger than AqBanking...

On 3/18/20 2:40 PM, John Ralls wrote:



On Mar 18, 2020, at 9:33 AM, Christopher Singley  wrote:

You're sending VERSION="220", which USAA doesn't accept.  You need to send VERSION="200" 
or VERSION="202".  Try that.

No joy, I still get a 400 response, but it does occur to me that it isn't 
necessarily an OFX issue, it could be that the HTTP request itself is malformed.






20200318122832


ENG

USAA
24591

QWIN
2300




20200318122835


24591
XX


2020031000
2020031800
Y






Regards,
John Ralls

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

And why were you thinking that?

Regards,
John Ralls


> On Mar 18, 2020, at 1:05 PM, chris graves  wrote:
> 
> I was thinking that it could be the first two lines of your file below.
> 
>> On Mar 18, 2020, at 12:40 PM, John Ralls  wrote:
>> 
>> 
>> 
>>> On Mar 18, 2020, at 9:33 AM, Christopher Singley  wrote:
>>> 
>>> You're sending VERSION="220", which USAA doesn't accept.  You need to send 
>>> VERSION="200" or VERSION="202".  Try that.
>> 
>> No joy, I still get a 400 response, but it does occur to me that it isn't 
>> necessarily an OFX issue, it could be that the HTTP request itself is 
>> malformed.
>> 
>> 
>> 
>> 
>> 
>> 
>> 20200318122832
>> 
>> 
>> ENG
>> 
>> USAA
>> 24591
>> 
>> QWIN
>> 2300
>> 
>> 
>> 
>> 
>> 20200318122835
>> 
>> 
>> 24591
>> XX
>> 
>> 
>> 2020031000
>> 2020031800
>> Y
>> 
>> 
>> 
>> 
>> 
>> 
>> Regards,
>> John Ralls
>> ___
>> 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.
> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Christopher Singley]

Don't worry about that.  That's a standard OFXv2 header (i.e. compliant 
XML).  The other headers you were noting earlier are OFXv1 headers (i.e. 
the weird INI-formatted key: value pairs prepended to the SGML soup).


The problem I have is that USAA bank tells me it will speak OFXv2, and 
then returns an error when I try to do so.  And then furthermore returns 
an error for validly-formed OFXv1!


None of this using AqBanking, mind. Something has changed over at USAA.

On 3/18/20 3:05 PM, chris graves wrote:

I was thinking that it could be the first two lines of your file below.


On Mar 18, 2020, at 12:40 PM, John Ralls  wrote:




On Mar 18, 2020, at 9:33 AM, Christopher Singley  wrote:

You're sending VERSION="220", which USAA doesn't accept.  You need to send VERSION="200" 
or VERSION="202".  Try that.

No joy, I still get a 400 response, but it does occur to me that it isn't 
necessarily an OFX issue, it could be that the HTTP request itself is malformed.






20200318122832


ENG

USAA
24591

QWIN
2300




20200318122835


24591
XX


2020031000
2020031800
Y






Regards,
John Ralls
___
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.

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[chris graves]

Because I don't see them in the AQB5 ofx.log file and to me they look like XML 
syntax.  Not being knowledgeable on the subject I can't say for sure.  I 
thought at v1.6, the syntax was pure SMGL.  But again, I don't know what I 
don't know.

> On Mar 18, 2020, at 1:12 PM, John Ralls  wrote:
> 
> And why were you thinking that?
> 
> Regards,
> John Ralls
> 
> 
>> On Mar 18, 2020, at 1:05 PM, chris graves  wrote:
>> 
>> I was thinking that it could be the first two lines of your file below.
>> 
>>> On Mar 18, 2020, at 12:40 PM, John Ralls  wrote:
>>> 
>>> 
>>> 
 On Mar 18, 2020, at 9:33 AM, Christopher Singley  
 wrote:
 
 You're sending VERSION="220", which USAA doesn't accept.  You need to send 
 VERSION="200" or VERSION="202".  Try that.
>>> 
>>> No joy, I still get a 400 response, but it does occur to me that it isn't 
>>> necessarily an OFX issue, it could be that the HTTP request itself is 
>>> malformed.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 20200318122832
>>> 
>>> 
>>> ENG
>>> 
>>> USAA
>>> 24591
>>> 
>>> QWIN
>>> 2300
>>> 
>>> 
>>> 
>>> 
>>> 20200318122835
>>> 
>>> 
>>> 24591
>>> XX
>>> 
>>> 
>>> 2020031000
>>> 2020031800
>>> Y
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Regards,
>>> John Ralls
>>> ___
>>> 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.
>> 
> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

That would be because they are XML syntax. OFX V2 is XML.

Regards,
John Ralls


> On Mar 18, 2020, at 1:15 PM, chris graves  wrote:
> 
> Because I don't see them in the AQB5 ofx.log file and to me they look like 
> XML syntax.  Not being knowledgeable on the subject I can't say for sure.  I 
> thought at v1.6, the syntax was pure SMGL.  But again, I don't know what I 
> don't know.
> 
>> On Mar 18, 2020, at 1:12 PM, John Ralls  wrote:
>> 
>> And why were you thinking that?
>> 
>> Regards,
>> John Ralls
>> 
>> 
>>> On Mar 18, 2020, at 1:05 PM, chris graves  wrote:
>>> 
>>> I was thinking that it could be the first two lines of your file below.
>>> 
 On Mar 18, 2020, at 12:40 PM, John Ralls  wrote:
 
 
 
> On Mar 18, 2020, at 9:33 AM, Christopher Singley  
> wrote:
> 
> You're sending VERSION="220", which USAA doesn't accept.  You need to 
> send VERSION="200" or VERSION="202".  Try that.
 
 No joy, I still get a 400 response, but it does occur to me that it isn't 
 necessarily an OFX issue, it could be that the HTTP request itself is 
 malformed.
 
 
 
 
 
 
 20200318122832
 
 
 ENG
 
 USAA
 24591
 
 QWIN
 2300
 
 
 
 
 20200318122835
 
 
 24591
 XX
 
 
 2020031000
 2020031800
 Y
 
 
 
 
 
 
 Regards,
 John Ralls
 ___
 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.
>>> 
>> 
> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[chris graves]

But I'm using (or trying to use) OFX V1.

> On Mar 18, 2020, at 1:23 PM, John Ralls  wrote:
> 
> That would be because they are XML syntax. OFX V2 is XML.
> 
> Regards,
> John Ralls
> 
> 
>> On Mar 18, 2020, at 1:15 PM, chris graves  wrote:
>> 
>> Because I don't see them in the AQB5 ofx.log file and to me they look like 
>> XML syntax.  Not being knowledgeable on the subject I can't say for sure.  I 
>> thought at v1.6, the syntax was pure SMGL.  But again, I don't know what I 
>> don't know.
>> 
>>> On Mar 18, 2020, at 1:12 PM, John Ralls  wrote:
>>> 
>>> And why were you thinking that?
>>> 
>>> Regards,
>>> John Ralls
>>> 
>>> 
 On Mar 18, 2020, at 1:05 PM, chris graves  wrote:
 
 I was thinking that it could be the first two lines of your file below.
 
> On Mar 18, 2020, at 12:40 PM, John Ralls  wrote:
> 
> 
> 
>> On Mar 18, 2020, at 9:33 AM, Christopher Singley  
>> wrote:
>> 
>> You're sending VERSION="220", which USAA doesn't accept.  You need to 
>> send VERSION="200" or VERSION="202".  Try that.
> 
> No joy, I still get a 400 response, but it does occur to me that it isn't 
> necessarily an OFX issue, it could be that the HTTP request itself is 
> malformed.
> 
> 
> 
> 
> 
> 
> 20200318122832
> 
> 
> ENG
> 
> USAA
> 24591
> 
> QWIN
> 2300
> 
> 
> 
> 
> 20200318122835
> 
> 
> 24591
> XX
> 
> 
> 2020031000
> 2020031800
> Y
> 
> 
> 
> 
> 
> 
> Regards,
> John Ralls
> ___
> 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.
 
>>> 
>> 
> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

Here is what I was thinking were significant differences found in ofx.log.
AQB5 vs git, which should be defaulting to OFX 1.

AQB5:
Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318081757.000

...

git:
Sending:
-


...

On Wed, Mar 18, 2020 at 1:23 PM John Ralls  wrote:

> That would be because they are XML syntax. OFX V2 is XML.
>
> Regards,
> John Ralls
>
>
> > On Mar 18, 2020, at 1:15 PM, chris graves  wrote:
> >
> > Because I don't see them in the AQB5 ofx.log file and to me they look
> like XML syntax.  Not being knowledgeable on the subject I can't say for
> sure.  I thought at v1.6, the syntax was pure SMGL.  But again, I don't
> know what I don't know.
> >
> >> On Mar 18, 2020, at 1:12 PM, John Ralls  wrote:
> >>
> >> And why were you thinking that?
> >>
> >> Regards,
> >> John Ralls
> >>
> >>
> >>> On Mar 18, 2020, at 1:05 PM, chris graves 
> wrote:
> >>>
> >>> I was thinking that it could be the first two lines of your file below.
> >>>
>  On Mar 18, 2020, at 12:40 PM, John Ralls  wrote:
> 
> 
> 
> > On Mar 18, 2020, at 9:33 AM, Christopher Singley 
> wrote:
> >
> > You're sending VERSION="220", which USAA doesn't accept.  You need
> to send VERSION="200" or VERSION="202".  Try that.
> 
>  No joy, I still get a 400 response, but it does occur to me that it
> isn't necessarily an OFX issue, it could be that the HTTP request itself is
> malformed.
> 
>  
>   OLDFILEUID="NONE"?>
>  
>  
>  
>  20200318122832
>  
>  
>  ENG
>  
>  USAA
>  24591
>  
>  QWIN
>  2300
>  
>  
>  
>  
>  20200318122835
>  
>  
>  24591
>  XX
>  
>  
>  2020031000
>  2020031800
>  Y
>  
>  
>  
>  
>  
> 
>  Regards,
>  John Ralls
>  ___
>  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.
> >>>
> >>
> >
>
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hi Chris,

could you please test the latest GIT version? It should create valid
OFXv1 requests now, however, I can't test it completely since I only
have access to an OFXv2 server...


Regards
Martin


Am 18.03.20 um 16:31 schrieb chris graves:
> An additional bit of information from /tmp/ofx.log: 
> AQB5:
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318081757.000
> 
> ...
[...]


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] European electronic invoicing standard

[Frank H. Ellenberger]

Hello Michael,

Am 18.03.20 um 17:37 schrieb Michael L. Wilson:
> Greetings,
> 
> Might someone be able to confirm whether GnuCash is able to issue
> invoices in line with the European electronic invoicing standard?

1. GnuCash has, at least until now, no eInvoice ability.

2. There is no B2B standard. The "European electronic invoicing standard".

> https://ec.europa.eu/growth/single-market/public-procurement/digital/einvoicing_en

mentions a very vaguely directive
http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014L0055&locale=en
"on electronic invoicing in *public* procurement"

Since 18 April 2018 *Public authorities* across the EU should now be
able to process eInvoices respecting the European Standard.

About standardisation
e-invoicing-standardisation-overview-issues-and-conclusions-for-future-actions_en
https://ec.europa.eu/docsroom/documents/10472/attachments/1/translations/en/renditions/native
was the beginning.

The current standards indexed at
https://standards.cen.eu/dyn/www/f?p=204:32:0FSP_ORG_ID,FSP_LANG_ID:1883209,25&cs=126F1BDBC8D6D6141F550EB578B4A9CF4

> If any documentation exists concerning this, it would be greatly
> appreciated.
> 
> Michael

As I am not invoicing the government, I will not implement this.
If you are interested to implement that, we will support you.

Regards
Frank
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Christopher Singley]

See the top post on this thread - John Ralls reporting that git only 
speaks OFXv2.  However many banks only speak OFXv1.


I can confirm that I can download from USAA by speaking OFXv1.0.2.

I can no longer speak OFXv2 to USAA; something has changed on their side.

Sorry John, no workaround yet.

On 3/18/20 3:30 PM, Chris Graves wrote:

Here is what I was thinking were significant differences found in ofx.log.
AQB5 vs git, which should be defaulting to OFX 1.

AQB5:
Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318081757.000

...

git:
Sending:
-


...

On Wed, Mar 18, 2020 at 1:23 PM John Ralls > wrote:


That would be because they are XML syntax. OFX V2 is XML.

Regards,
John Ralls


> On Mar 18, 2020, at 1:15 PM, chris graves mailto:mohaveba...@gmail.com>> wrote:
>
> Because I don't see them in the AQB5 ofx.log file and to me they
look like XML syntax.  Not being knowledgeable on the subject I
can't say for sure.  I thought at v1.6, the syntax was pure SMGL. 
But again, I don't know what I don't know.
>
>> On Mar 18, 2020, at 1:12 PM, John Ralls mailto:jra...@ceridwen.us>> wrote:
>>
>> And why were you thinking that?
>>
>> Regards,
>> John Ralls
>>
>>
>>> On Mar 18, 2020, at 1:05 PM, chris graves
mailto:mohaveba...@gmail.com>> wrote:
>>>
>>> I was thinking that it could be the first two lines of your
file below.
>>>
 On Mar 18, 2020, at 12:40 PM, John Ralls mailto:jra...@ceridwen.us>> wrote:



> On Mar 18, 2020, at 9:33 AM, Christopher Singley
mailto:csing...@gmail.com>> wrote:
>
> You're sending VERSION="220", which USAA doesn't accept. 
You need to send VERSION="200" or VERSION="202".  Try that.

 No joy, I still get a 400 response, but it does occur to me
that it isn't necessarily an OFX issue, it could be that the HTTP
request itself is malformed.

 
 
 
 
 
 20200318122832
 
 
 ENG
 
 USAA
 24591
 
 QWIN
 2300
 
 
 
 
 20200318122835
 
 
 24591
 XX
 
 
 2020031000
 2020031800
 Y
 
 
 
 
 

 Regards,
 John Ralls
 ___
 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.
>>>
>>
>


___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

Hi Martin,

Looking better!  However, to my knowledge, my bank only supports OFX
version 102 or 103.  I had been using 102.

ofx.log:
Sending:
-
OFXHEADER:220
DATA:OFXSGML
VERSION:220
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318135033.000




20200318135025.000

On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss  wrote:

> Hi Chris,
>
> could you please test the latest GIT version? It should create valid
> OFXv1 requests now, however, I can't test it completely since I only
> have access to an OFXv2 server...
>
>
> Regards
> Martin
>
>
> Am 18.03.20 um 16:31 schrieb chris graves:
> > An additional bit of information from /tmp/ofx.log:
> > AQB5:
> > Sending:
> > -
> > OFXHEADER:100
> > DATA:OFXSGML
> > VERSION:102
> > SECURITY:NONE
> > ENCODING:USASCII
> > CHARSET:1252
> > COMPRESSION:NONE
> > OLDFILEUID:NONE
> > NEWFILEUID:20200318081757.000
> >
> > ...
> [...]
>
>
> --
> "Things are only impossible until they're not"
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[chris graves]

I think that would have been a mistake, git defaults to OFXv1.

> On Mar 18, 2020, at 1:38 PM, Christopher Singley  wrote:
> 
> See the top post on this thread - John Ralls reporting that git only speaks 
> OFXv2.  However many banks only speak OFXv1.
> 
> I can confirm that I can download from USAA by speaking OFXv1.0.2.
> 
> I can no longer speak OFXv2 to USAA; something has changed on their side.
> 
> Sorry John, no workaround yet.
> 
> On 3/18/20 3:30 PM, Chris Graves wrote:
>> Here is what I was thinking were significant differences found in ofx.log.
>> AQB5 vs git, which should be defaulting to OFX 1.
>> 
>> AQB5:
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318081757.000
>> 
>> ...
>> 
>> git:
>> Sending:
>> -
>> 
>> 
>> ...
>> 
>> On Wed, Mar 18, 2020 at 1:23 PM John Ralls > > wrote:
>> That would be because they are XML syntax. OFX V2 is XML.
>> 
>> Regards,
>> John Ralls
>> 
>> 
>> > On Mar 18, 2020, at 1:15 PM, chris graves > > > wrote:
>> > 
>> > Because I don't see them in the AQB5 ofx.log file and to me they look like 
>> > XML syntax.  Not being knowledgeable on the subject I can't say for sure.  
>> > I thought at v1.6, the syntax was pure SMGL.  But again, I don't know what 
>> > I don't know.
>> > 
>> >> On Mar 18, 2020, at 1:12 PM, John Ralls > >> > wrote:
>> >> 
>> >> And why were you thinking that?
>> >> 
>> >> Regards,
>> >> John Ralls
>> >> 
>> >> 
>> >>> On Mar 18, 2020, at 1:05 PM, chris graves > >>> > wrote:
>> >>> 
>> >>> I was thinking that it could be the first two lines of your file below.
>> >>> 
>>  On Mar 18, 2020, at 12:40 PM, John Ralls >  > wrote:
>>  
>>  
>>  
>> > On Mar 18, 2020, at 9:33 AM, Christopher Singley > > > wrote:
>> > 
>> > You're sending VERSION="220", which USAA doesn't accept.  You need to 
>> > send VERSION="200" or VERSION="202".  Try that.
>>  
>>  No joy, I still get a 400 response, but it does occur to me that it 
>>  isn't necessarily an OFX issue, it could be that the HTTP request 
>>  itself is malformed.
>>  
>>  
>>  
>>  
>>  
>>  
>>  20200318122832
>>  
>>  
>>  ENG
>>  
>>  USAA
>>  24591
>>  
>>  QWIN
>>  2300
>>  
>>  
>>  
>>  
>>  20200318122835
>>  
>>  
>>  24591
>>  XX
>>  
>>  
>>  2020031000
>>  2020031800
>>  Y
>>  
>>  
>>  
>>  
>>  
>>  
>>  Regards,
>>  John Ralls
>>  ___
>>  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.
>> >>> 
>> >> 
>> > 
>> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hi,

you can change the header manually to 102/103 in the homebanking setup
dialog (select user, edit user, switch to app settings and type-in
header version 102).

Regards
Martin


Am 18.03.20 um 21:57 schrieb Chris Graves:
> Hi Martin,
> 
> Looking better!  However, to my knowledge, my bank only supports OFX
> version 102 or 103.  I had been using 102.
> 
> ofx.log:
> Sending:
> -
> OFXHEADER:220
> DATA:OFXSGML
> VERSION:220
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318135033.000
> 
> 
> 
> 
> 20200318135025.000
> 
> On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss  > wrote:
> 
> Hi Chris,
> 
> could you please test the latest GIT version? It should create valid
> OFXv1 requests now, however, I can't test it completely since I only
> have access to an OFXv2 server...
> 
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 16:31 schrieb chris graves:
> > An additional bit of information from /tmp/ofx.log:
> > AQB5:
> > Sending:
> > -
> > OFXHEADER:100
> > DATA:OFXSGML
> > VERSION:102
> > SECURITY:NONE
> > ENCODING:USASCII
> > CHARSET:1252
> > COMPRESSION:NONE
> > OLDFILEUID:NONE
> > NEWFILEUID:20200318081757.000
> >
> > ...
> [...]
> 
> 
> -- 
> "Things are only impossible until they're not"
> 


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

Nice!  I see that the change has been made, but still receive the HTTP 400
error.

In the AQB5 ofx.log file for a successful case, I see
OFXHEADER:100
VERSION:102

In the AQB6 file, I see
OFXHEADER:102
VERSION:102

Not sure if this could be the problem.  Is there a way to set OFXHEADER and
VERSION independently?


On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss  wrote:

> Hi,
>
> you can change the header manually to 102/103 in the homebanking setup
> dialog (select user, edit user, switch to app settings and type-in
> header version 102).
>
> Regards
> Martin
>
>
> Am 18.03.20 um 21:57 schrieb Chris Graves:
> > Hi Martin,
> >
> > Looking better!  However, to my knowledge, my bank only supports OFX
> > version 102 or 103.  I had been using 102.
> >
> > ofx.log:
> > Sending:
> > -
> > OFXHEADER:220
> > DATA:OFXSGML
> > VERSION:220
> > SECURITY:NONE
> > ENCODING:USASCII
> > CHARSET:1252
> > COMPRESSION:NONE
> > OLDFILEUID:NONE
> > NEWFILEUID:20200318135033.000
> >
> > 
> > 
> > 
> > 20200318135025.000
> >
> > On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss  > > wrote:
> >
> > Hi Chris,
> >
> > could you please test the latest GIT version? It should create valid
> > OFXv1 requests now, however, I can't test it completely since I only
> > have access to an OFXv2 server...
> >
> >
> > Regards
> > Martin
> >
> >
> > Am 18.03.20 um 16:31 schrieb chris graves:
> > > An additional bit of information from /tmp/ofx.log:
> > > AQB5:
> > > Sending:
> > > -
> > > OFXHEADER:100
> > > DATA:OFXSGML
> > > VERSION:102
> > > SECURITY:NONE
> > > ENCODING:USASCII
> > > CHARSET:1252
> > > COMPRESSION:NONE
> > > OLDFILEUID:NONE
> > > NEWFILEUID:20200318081757.000
> > >
> > > ...
> > [...]
> >
> >
> > --
> > "Things are only impossible until they're not"
> >
>
>
> --
> "Things are only impossible until they're not"
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hi,

not ATM, but that can be arranged. However, how about leaving that field
empty in the settings dialog? That should default to 100 for OFXHEADER
and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
good^H^H^H reasons for those mixed defaults... :-})

Regards
Martin


Am 18.03.20 um 22:26 schrieb Chris Graves:
> Nice!  I see that the change has been made, but still receive the HTTP
> 400 error.
> 
> In the AQB5 ofx.log file for a successful case, I see
> OFXHEADER:100
> VERSION:102
> 
> In the AQB6 file, I see
> OFXHEADER:102
> VERSION:102
> 
> Not sure if this could be the problem.  Is there a way to set OFXHEADER
> and VERSION independently?
> 
> 
> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss  > wrote:
> 
> Hi,
> 
> you can change the header manually to 102/103 in the homebanking setup
> dialog (select user, edit user, switch to app settings and type-in
> header version 102).
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 21:57 schrieb Chris Graves:
> > Hi Martin,
> >
> > Looking better!  However, to my knowledge, my bank only supports OFX
> > version 102 or 103.  I had been using 102.
> >
> > ofx.log:
> > Sending:
> > -
> > OFXHEADER:220
> > DATA:OFXSGML
> > VERSION:220
> > SECURITY:NONE
> > ENCODING:USASCII
> > CHARSET:1252
> > COMPRESSION:NONE
> > OLDFILEUID:NONE
> > NEWFILEUID:20200318135033.000
> >
> > 
> > 
> > 
> > 20200318135025.000
> >
> > On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss  
> > >> wrote:
> >
> >     Hi Chris,
> >
> >     could you please test the latest GIT version? It should create
> valid
> >     OFXv1 requests now, however, I can't test it completely since
> I only
> >     have access to an OFXv2 server...
> >
> >
> >     Regards
> >     Martin
> >
> >
> >     Am 18.03.20 um 16:31 schrieb chris graves:
> >     > An additional bit of information from /tmp/ofx.log:
> >     > AQB5:
> >     > Sending:
> >     > -
> >     > OFXHEADER:100
> >     > DATA:OFXSGML
> >     > VERSION:102
> >     > SECURITY:NONE
> >     > ENCODING:USASCII
> >     > CHARSET:1252
> >     > COMPRESSION:NONE
> >     > OLDFILEUID:NONE
> >     > NEWFILEUID:20200318081757.000
> >     >
> >     > ...
> >     [...]
> >
> >
> >     --
> >     "Things are only impossible until they're not"
> >
> 
> 
> -- 
> "Things are only impossible until they're not"
> 


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

It won't let you leave that blank, and even if it did it would put '100' in 
both fields:
 if (!(s && *s))
s="100";

  GWEN_Buffer_AppendString(buf, "OFXHEADER:");
  GWEN_Buffer_AppendString(buf, s);
  GWEN_Buffer_AppendString(buf, "\r\nDATA:OFXSGML\r\n");

  GWEN_Buffer_AppendString(buf, "VERSION:");
  s=AO_User_GetHeaderVer(u);
  if (!s || !*s)
s="102";
  GWEN_Buffer_AppendString(buf, s);
  GWEN_Buffer_AppendString(buf, "\r\n");

Because at the second test s has a value.

The new code doesn't emit the trailing tags, so that may not have been the 
problem. The main difference other than the OFXHEADER: value now appears to be 
that there are newlines between the fields. Are those getting escaped in 
GWEN_SyncIo_Http_Write?

Regards,
John Ralls
> On Mar 18, 2020, at 2:34 PM, Martin Preuss  wrote:
> 
> Hi,
> 
> not ATM, but that can be arranged. However, how about leaving that field
> empty in the settings dialog? That should default to 100 for OFXHEADER
> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
> good^H^H^H reasons for those mixed defaults... :-})
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 22:26 schrieb Chris Graves:
>> Nice!  I see that the change has been made, but still receive the HTTP
>> 400 error.
>> 
>> In the AQB5 ofx.log file for a successful case, I see
>> OFXHEADER:100
>> VERSION:102
>> 
>> In the AQB6 file, I see
>> OFXHEADER:102
>> VERSION:102
>> 
>> Not sure if this could be the problem.  Is there a way to set OFXHEADER
>> and VERSION independently?
>> 
>> 
>> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss > > wrote:
>> 
>>Hi,
>> 
>>you can change the header manually to 102/103 in the homebanking setup
>>dialog (select user, edit user, switch to app settings and type-in
>>header version 102).
>> 
>>Regards
>>Martin
>> 
>> 
>>Am 18.03.20 um 21:57 schrieb Chris Graves:
>>> Hi Martin,
>>> 
>>> Looking better!  However, to my knowledge, my bank only supports OFX
>>> version 102 or 103.  I had been using 102.
>>> 
>>> ofx.log:
>>> Sending:
>>> -
>>> OFXHEADER:220
>>> DATA:OFXSGML
>>> VERSION:220
>>> SECURITY:NONE
>>> ENCODING:USASCII
>>> CHARSET:1252
>>> COMPRESSION:NONE
>>> OLDFILEUID:NONE
>>> NEWFILEUID:20200318135033.000
>>> 
>>> 
>>> 
>>> 
>>> 20200318135025.000
>>> 
>>> On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss >
>>> >> wrote:
>>> 
>>>  Hi Chris,
>>> 
>>>  could you please test the latest GIT version? It should create
>>valid
>>>  OFXv1 requests now, however, I can't test it completely since
>>I only
>>>  have access to an OFXv2 server...
>>> 
>>> 
>>>  Regards
>>>  Martin
>>> 
>>> 
>>>  Am 18.03.20 um 16:31 schrieb chris graves:
>>>  > An additional bit of information from /tmp/ofx.log:
>>>  > AQB5:
>>>  > Sending:
>>>  > -
>>>  > OFXHEADER:100
>>>  > DATA:OFXSGML
>>>  > VERSION:102
>>>  > SECURITY:NONE
>>>  > ENCODING:USASCII
>>>  > CHARSET:1252
>>>  > COMPRESSION:NONE
>>>  > OLDFILEUID:NONE
>>>  > NEWFILEUID:20200318081757.000
>>>  >
>>>  > ...
>>>  [...]
>>> 
>>> 
>>>  --
>>>  "Things are only impossible until they're not"
>>> 
>> 
>> 
>>-- 
>>"Things are only impossible until they're not"
>> 
> 
> 
> -- 
> "Things are only impossible until they're not"

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

Hi Martin,

The GUI wouldn't let me leave that field blank, so I manually deleted the
entry from the .conf file. Running again, it did use the defaults that you
specified.  However, still the http 400 error and no response.

Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318144035.000

On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss  wrote:

> Hi,
>
> not ATM, but that can be arranged. However, how about leaving that field
> empty in the settings dialog? That should default to 100 for OFXHEADER
> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
> good^H^H^H reasons for those mixed defaults... :-})
>
> Regards
> Martin
>
>
> Am 18.03.20 um 22:26 schrieb Chris Graves:
> > Nice!  I see that the change has been made, but still receive the HTTP
> > 400 error.
> >
> > In the AQB5 ofx.log file for a successful case, I see
> > OFXHEADER:100
> > VERSION:102
> >
> > In the AQB6 file, I see
> > OFXHEADER:102
> > VERSION:102
> >
> > Not sure if this could be the problem.  Is there a way to set OFXHEADER
> > and VERSION independently?
> >
> >
> > On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss  > > wrote:
> >
> > Hi,
> >
> > you can change the header manually to 102/103 in the homebanking
> setup
> > dialog (select user, edit user, switch to app settings and type-in
> > header version 102).
> >
> > Regards
> > Martin
> >
> >
> > Am 18.03.20 um 21:57 schrieb Chris Graves:
> > > Hi Martin,
> > >
> > > Looking better!  However, to my knowledge, my bank only supports
> OFX
> > > version 102 or 103.  I had been using 102.
> > >
> > > ofx.log:
> > > Sending:
> > > -
> > > OFXHEADER:220
> > > DATA:OFXSGML
> > > VERSION:220
> > > SECURITY:NONE
> > > ENCODING:USASCII
> > > CHARSET:1252
> > > COMPRESSION:NONE
> > > OLDFILEUID:NONE
> > > NEWFILEUID:20200318135033.000
> > >
> > > 
> > > 
> > > 
> > > 20200318135025.000
> > >
> > > On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss  > 
> > > >> wrote:
> > >
> > > Hi Chris,
> > >
> > > could you please test the latest GIT version? It should create
> > valid
> > > OFXv1 requests now, however, I can't test it completely since
> > I only
> > > have access to an OFXv2 server...
> > >
> > >
> > > Regards
> > > Martin
> > >
> > >
> > > Am 18.03.20 um 16:31 schrieb chris graves:
> > > > An additional bit of information from /tmp/ofx.log:
> > > > AQB5:
> > > > Sending:
> > > > -
> > > > OFXHEADER:100
> > > > DATA:OFXSGML
> > > > VERSION:102
> > > > SECURITY:NONE
> > > > ENCODING:USASCII
> > > > CHARSET:1252
> > > > COMPRESSION:NONE
> > > > OLDFILEUID:NONE
> > > > NEWFILEUID:20200318081757.000
> > > >
> > > > ...
> > > [...]
> > >
> > >
> > > --
> > > "Things are only impossible until they're not"
> > >
> >
> >
> > --
> > "Things are only impossible until they're not"
> >
>
>
> --
> "Things are only impossible until they're not"
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

I changed the line just below OFXHEADER to 
GWEN_Buffer_AppendString(buf, "100");

producing the following. No luck, it still returns a 400 error.

Regards,
John Ralls

Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318144822.000




20200318144819


ENG

USAA
24591

QWIN
2300




20200318144822


24591



2020030900
2020031800
Y






> On Mar 18, 2020, at 2:47 PM, John Ralls  wrote:
> 
> It won't let you leave that blank, and even if it did it would put '100' in 
> both fields:
> if (!(s && *s))
>s="100";
> 
>  GWEN_Buffer_AppendString(buf, "OFXHEADER:");
>  GWEN_Buffer_AppendString(buf, s);
>  GWEN_Buffer_AppendString(buf, "\r\nDATA:OFXSGML\r\n");
> 
>  GWEN_Buffer_AppendString(buf, "VERSION:");
>  s=AO_User_GetHeaderVer(u);
>  if (!s || !*s)
>s="102";
>  GWEN_Buffer_AppendString(buf, s);
>  GWEN_Buffer_AppendString(buf, "\r\n");
> 
> Because at the second test s has a value.
> 
> The new code doesn't emit the trailing tags, so that may not have been the 
> problem. The main difference other than the OFXHEADER: value now appears to 
> be that there are newlines between the fields. Are those getting escaped in 
> GWEN_SyncIo_Http_Write?
> 
> Regards,
> John Ralls
>> On Mar 18, 2020, at 2:34 PM, Martin Preuss  wrote:
>> 
>> Hi,
>> 
>> not ATM, but that can be arranged. However, how about leaving that field
>> empty in the settings dialog? That should default to 100 for OFXHEADER
>> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
>> good^H^H^H reasons for those mixed defaults... :-})
>> 
>> Regards
>> Martin
>> 
>> 
>> Am 18.03.20 um 22:26 schrieb Chris Graves:
>>> Nice!  I see that the change has been made, but still receive the HTTP
>>> 400 error.
>>> 
>>> In the AQB5 ofx.log file for a successful case, I see
>>> OFXHEADER:100
>>> VERSION:102
>>> 
>>> In the AQB6 file, I see
>>> OFXHEADER:102
>>> VERSION:102
>>> 
>>> Not sure if this could be the problem.  Is there a way to set OFXHEADER
>>> and VERSION independently?
>>> 
>>> 
>>> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >> > wrote:
>>> 
>>>   Hi,
>>> 
>>>   you can change the header manually to 102/103 in the homebanking setup
>>>   dialog (select user, edit user, switch to app settings and type-in
>>>   header version 102).
>>> 
>>>   Regards
>>>   Martin
>>> 
>>> 
>>>   Am 18.03.20 um 21:57 schrieb Chris Graves:
 Hi Martin,
 
 Looking better!  However, to my knowledge, my bank only supports OFX
 version 102 or 103.  I had been using 102.
 
 ofx.log:
 Sending:
 -
 OFXHEADER:220
 DATA:OFXSGML
 VERSION:220
 SECURITY:NONE
 ENCODING:USASCII
 CHARSET:1252
 COMPRESSION:NONE
 OLDFILEUID:NONE
 NEWFILEUID:20200318135033.000
 
 
 
 
 20200318135025.000
 
 On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss >>   
 >> wrote:
 
 Hi Chris,
 
 could you please test the latest GIT version? It should create
>>>   valid
 OFXv1 requests now, however, I can't test it completely since
>>>   I only
 have access to an OFXv2 server...
 
 
 Regards
 Martin
 
 
 Am 18.03.20 um 16:31 schrieb chris graves:
> An additional bit of information from /tmp/ofx.log:
> AQB5:
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318081757.000
> 
> ...
 [...]
 
 
 --
 "Things are only impossible until they're not"
 
>>> 
>>> 
>>>   -- 
>>>   "Things are only impossible until they're not"
>>> 
>> 
>> 
>> -- 
>> "Things are only impossible until they're not"
> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hi,

okay now, the latest GIT version always sets "OFXHEADER:100" and uses
the given header version only for the "VERSION:" header. In that case
you can specify "102" and it should create the correct headers...

Please note: For reasons not yet understood it might be necessary when
updating from git to first issue "make clean" before "make", otherwise
sometimes the resulting binaries might not be based on all the latest
code (I have no idea whether this happens for others as well, it's just
something I stumbled upon while working on AqBanking).


Regards
Martin


Am 18.03.20 um 22:47 schrieb John Ralls:
> It won't let you leave that blank, and even if it did it would put '100' in 
> both fields:
>  if (!(s && *s))
> s="100";
> 
>   GWEN_Buffer_AppendString(buf, "OFXHEADER:");
>   GWEN_Buffer_AppendString(buf, s);
>   GWEN_Buffer_AppendString(buf, "\r\nDATA:OFXSGML\r\n");
> 
>   GWEN_Buffer_AppendString(buf, "VERSION:");
>   s=AO_User_GetHeaderVer(u);
>   if (!s || !*s)
> s="102";
>   GWEN_Buffer_AppendString(buf, s);
>   GWEN_Buffer_AppendString(buf, "\r\n");
> 
> Because at the second test s has a value.
> 
> The new code doesn't emit the trailing tags, so that may not have been the 
> problem. The main difference other than the OFXHEADER: value now appears to 
> be that there are newlines between the fields. Are those getting escaped in 
> GWEN_SyncIo_Http_Write?
> 
> Regards,
> John Ralls
>> On Mar 18, 2020, at 2:34 PM, Martin Preuss  wrote:
>>
>> Hi,
>>
>> not ATM, but that can be arranged. However, how about leaving that field
>> empty in the settings dialog? That should default to 100 for OFXHEADER
>> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
>> good^H^H^H reasons for those mixed defaults... :-})
>>
>> Regards
>> Martin
>>
>>
>> Am 18.03.20 um 22:26 schrieb Chris Graves:
>>> Nice!  I see that the change has been made, but still receive the HTTP
>>> 400 error.
>>>
>>> In the AQB5 ofx.log file for a successful case, I see
>>> OFXHEADER:100
>>> VERSION:102
>>>
>>> In the AQB6 file, I see
>>> OFXHEADER:102
>>> VERSION:102
>>>
>>> Not sure if this could be the problem.  Is there a way to set OFXHEADER
>>> and VERSION independently?
>>>
>>>
>>> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >> > wrote:
>>>
>>>Hi,
>>>
>>>you can change the header manually to 102/103 in the homebanking setup
>>>dialog (select user, edit user, switch to app settings and type-in
>>>header version 102).
>>>
>>>Regards
>>>Martin
>>>
>>>
>>>Am 18.03.20 um 21:57 schrieb Chris Graves:
 Hi Martin,

 Looking better!  However, to my knowledge, my bank only supports OFX
 version 102 or 103.  I had been using 102.

 ofx.log:
 Sending:
 -
 OFXHEADER:220
 DATA:OFXSGML
 VERSION:220
 SECURITY:NONE
 ENCODING:USASCII
 CHARSET:1252
 COMPRESSION:NONE
 OLDFILEUID:NONE
 NEWFILEUID:20200318135033.000

 
 
 
 20200318135025.000

 On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss >>
 >> wrote:

  Hi Chris,

  could you please test the latest GIT version? It should create
>>>valid
  OFXv1 requests now, however, I can't test it completely since
>>>I only
  have access to an OFXv2 server...


  Regards
  Martin


  Am 18.03.20 um 16:31 schrieb chris graves:
  > An additional bit of information from /tmp/ofx.log:
  > AQB5:
  > Sending:
  > -
  > OFXHEADER:100
  > DATA:OFXSGML
  > VERSION:102
  > SECURITY:NONE
  > ENCODING:USASCII
  > CHARSET:1252
  > COMPRESSION:NONE
  > OLDFILEUID:NONE
  > NEWFILEUID:20200318081757.000
  >
  > ...
  [...]


  --
  "Things are only impossible until they're not"

>>>
>>>
>>>-- 
>>>"Things are only impossible until they're not"
>>>
>>
>>
>> -- 
>> "Things are only impossible until they're not"
> 


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hi,

please see my other mail (latest GIT).

Maybe "103" then (I heard of some cases where "103" was necessary)? Or
perhaps "160"?

Will fix the gui btw...


Regards
Martin

Am 18.03.20 um 22:50 schrieb Chris Graves:
> Hi Martin,
> 
> The GUI wouldn't let me leave that field blank, so I manually deleted
> the entry from the .conf file. Running again, it did use the defaults
> that you specified.  However, still the http 400 error and no response.
> 
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318144035.000
> 
> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss  > wrote:
> 
> Hi,
> 
> not ATM, but that can be arranged. However, how about leaving that field
> empty in the settings dialog? That should default to 100 for OFXHEADER
> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
> good^H^H^H reasons for those mixed defaults... :-})
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 22:26 schrieb Chris Graves:
> > Nice!  I see that the change has been made, but still receive the HTTP
> > 400 error.
> >
> > In the AQB5 ofx.log file for a successful case, I see
> > OFXHEADER:100
> > VERSION:102
> >
> > In the AQB6 file, I see
> > OFXHEADER:102
> > VERSION:102
> >
> > Not sure if this could be the problem.  Is there a way to set
> OFXHEADER
> > and VERSION independently?
> >
> >
> > On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss  
> > >> wrote:
> >
> >     Hi,
> >
> >     you can change the header manually to 102/103 in the
> homebanking setup
> >     dialog (select user, edit user, switch to app settings and type-in
> >     header version 102).
> >
> >     Regards
> >     Martin
> >
> >
> >     Am 18.03.20 um 21:57 schrieb Chris Graves:
> >     > Hi Martin,
> >     >
> >     > Looking better!  However, to my knowledge, my bank only
> supports OFX
> >     > version 102 or 103.  I had been using 102.
> >     >
> >     > ofx.log:
> >     > Sending:
> >     > -
> >     > OFXHEADER:220
> >     > DATA:OFXSGML
> >     > VERSION:220
> >     > SECURITY:NONE
> >     > ENCODING:USASCII
> >     > CHARSET:1252
> >     > COMPRESSION:NONE
> >     > OLDFILEUID:NONE
> >     > NEWFILEUID:20200318135033.000
> >     >
> >     > 
> >     > 
> >     > 
> >     > 20200318135025.000
> >     >
> >     > On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss
> mailto:mar...@aqbanking.de>
> >     >
> >     > 
>  >     >
> >     >     Hi Chris,
> >     >
> >     >     could you please test the latest GIT version? It should
> create
> >     valid
> >     >     OFXv1 requests now, however, I can't test it completely
> since
> >     I only
> >     >     have access to an OFXv2 server...
> >     >
> >     >
> >     >     Regards
> >     >     Martin
> >     >
> >     >
> >     >     Am 18.03.20 um 16:31 schrieb chris graves:
> >     >     > An additional bit of information from /tmp/ofx.log:
> >     >     > AQB5:
> >     >     > Sending:
> >     >     > -
> >     >     > OFXHEADER:100
> >     >     > DATA:OFXSGML
> >     >     > VERSION:102
> >     >     > SECURITY:NONE
> >     >     > ENCODING:USASCII
> >     >     > CHARSET:1252
> >     >     > COMPRESSION:NONE
> >     >     > OLDFILEUID:NONE
> >     >     > NEWFILEUID:20200318081757.000
> >     >     >
> >     >     > ...
> >     >     [...]
> >     >
> >     >
> >     >     --
> >     >     "Things are only impossible until they're not"
> >     >
> >
> >
> >     --
> >     "Things are only impossible until they're not"
> >
> 
> 
> -- 
> "Things are only impossible until they're not"
> 


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hi again,

with the latest changes: Are there any probably important differences in
the generated OFX request compared to Aqb5's output (except dates etc.)?

Regards
Martin


Am 18.03.20 um 22:50 schrieb Chris Graves:
> Hi Martin,
> 
> The GUI wouldn't let me leave that field blank, so I manually deleted
> the entry from the .conf file. Running again, it did use the defaults
> that you specified.  However, still the http 400 error and no response.
> 
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318144035.000
> 
> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss  > wrote:
> 
> Hi,
> 
> not ATM, but that can be arranged. However, how about leaving that field
> empty in the settings dialog? That should default to 100 for OFXHEADER
> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
> good^H^H^H reasons for those mixed defaults... :-})
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 22:26 schrieb Chris Graves:
> > Nice!  I see that the change has been made, but still receive the HTTP
> > 400 error.
> >
> > In the AQB5 ofx.log file for a successful case, I see
> > OFXHEADER:100
> > VERSION:102
> >
> > In the AQB6 file, I see
> > OFXHEADER:102
> > VERSION:102
> >
> > Not sure if this could be the problem.  Is there a way to set
> OFXHEADER
> > and VERSION independently?
> >
> >
> > On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss  
> > >> wrote:
> >
> >     Hi,
> >
> >     you can change the header manually to 102/103 in the
> homebanking setup
> >     dialog (select user, edit user, switch to app settings and type-in
> >     header version 102).
> >
> >     Regards
> >     Martin
> >
> >
> >     Am 18.03.20 um 21:57 schrieb Chris Graves:
> >     > Hi Martin,
> >     >
> >     > Looking better!  However, to my knowledge, my bank only
> supports OFX
> >     > version 102 or 103.  I had been using 102.
> >     >
> >     > ofx.log:
> >     > Sending:
> >     > -
> >     > OFXHEADER:220
> >     > DATA:OFXSGML
> >     > VERSION:220
> >     > SECURITY:NONE
> >     > ENCODING:USASCII
> >     > CHARSET:1252
> >     > COMPRESSION:NONE
> >     > OLDFILEUID:NONE
> >     > NEWFILEUID:20200318135033.000
> >     >
> >     > 
> >     > 
> >     > 
> >     > 20200318135025.000
> >     >
> >     > On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss
> mailto:mar...@aqbanking.de>
> >     >
> >     > 
>  >     >
> >     >     Hi Chris,
> >     >
> >     >     could you please test the latest GIT version? It should
> create
> >     valid
> >     >     OFXv1 requests now, however, I can't test it completely
> since
> >     I only
> >     >     have access to an OFXv2 server...
> >     >
> >     >
> >     >     Regards
> >     >     Martin
> >     >
> >     >
> >     >     Am 18.03.20 um 16:31 schrieb chris graves:
> >     >     > An additional bit of information from /tmp/ofx.log:
> >     >     > AQB5:
> >     >     > Sending:
> >     >     > -
> >     >     > OFXHEADER:100
> >     >     > DATA:OFXSGML
> >     >     > VERSION:102
> >     >     > SECURITY:NONE
> >     >     > ENCODING:USASCII
> >     >     > CHARSET:1252
> >     >     > COMPRESSION:NONE
> >     >     > OLDFILEUID:NONE
> >     >     > NEWFILEUID:20200318081757.000
> >     >     >
> >     >     > ...
> >     >     [...]
> >     >
> >     >
> >     >     --
> >     >     "Things are only impossible until they're not"
> >     >
> >
> >
> >     --
> >     "Things are only impossible until they're not"
> >
> 
> 
> -- 
> "Things are only impossible until they're not"
> 


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[chris graves]

Not sure if it matters, but the OFX clause/aggregate? in AQB5 is on three lines 
with a line break after the USERID and again after USERPASS.

In git, there is a linebreak after each element/aggregate.

> On Mar 18, 2020, at 2:51 PM, John Ralls  wrote:
> 
> I changed the line just below OFXHEADER to 
>GWEN_Buffer_AppendString(buf, "100");
> 
> producing the following. No luck, it still returns a 400 error.
> 
> Regards,
> John Ralls
> 
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318144822.000
> 
> 
> 
> 
> 20200318144819
> 
> 
> ENG
> 
> USAA
> 24591
> 
> QWIN
> 2300
> 
> 
> 
> 
> 20200318144822
> 
> 
> 24591
> 
> 
> 
> 2020030900
> 2020031800
> Y
> 
> 
> 
> 
> 
> 
>> On Mar 18, 2020, at 2:47 PM, John Ralls  wrote:
>> 
>> It won't let you leave that blank, and even if it did it would put '100' in 
>> both fields:
>> if (!(s && *s))
>>   s="100";
>> 
>> GWEN_Buffer_AppendString(buf, "OFXHEADER:");
>> GWEN_Buffer_AppendString(buf, s);
>> GWEN_Buffer_AppendString(buf, "\r\nDATA:OFXSGML\r\n");
>> 
>> GWEN_Buffer_AppendString(buf, "VERSION:");
>> s=AO_User_GetHeaderVer(u);
>> if (!s || !*s)
>>   s="102";
>> GWEN_Buffer_AppendString(buf, s);
>> GWEN_Buffer_AppendString(buf, "\r\n");
>> 
>> Because at the second test s has a value.
>> 
>> The new code doesn't emit the trailing tags, so that may not have been the 
>> problem. The main difference other than the OFXHEADER: value now appears to 
>> be that there are newlines between the fields. Are those getting escaped in 
>> GWEN_SyncIo_Http_Write?
>> 
>> Regards,
>> John Ralls
>>> On Mar 18, 2020, at 2:34 PM, Martin Preuss  wrote:
>>> 
>>> Hi,
>>> 
>>> not ATM, but that can be arranged. However, how about leaving that field
>>> empty in the settings dialog? That should default to 100 for OFXHEADER
>>> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
>>> good^H^H^H reasons for those mixed defaults... :-})
>>> 
>>> Regards
>>> Martin
>>> 
>>> 
>>> Am 18.03.20 um 22:26 schrieb Chris Graves:
 Nice!  I see that the change has been made, but still receive the HTTP
 400 error.
 
 In the AQB5 ofx.log file for a successful case, I see
 OFXHEADER:100
 VERSION:102
 
 In the AQB6 file, I see
 OFXHEADER:102
 VERSION:102
 
 Not sure if this could be the problem.  Is there a way to set OFXHEADER
 and VERSION independently?
 
 
 On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >>> > wrote:
 
  Hi,
 
  you can change the header manually to 102/103 in the homebanking setup
  dialog (select user, edit user, switch to app settings and type-in
  header version 102).
 
  Regards
  Martin
 
 
  Am 18.03.20 um 21:57 schrieb Chris Graves:
> Hi Martin,
> 
> Looking better!  However, to my knowledge, my bank only supports OFX
> version 102 or 103.  I had been using 102.
> 
> ofx.log:
> Sending:
> -
> OFXHEADER:220
> DATA:OFXSGML
> VERSION:220
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318135033.000
> 
> 
> 
> 
> 20200318135025.000
> 
> On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss >>>  
> >> wrote:
> 
>Hi Chris,
> 
>could you please test the latest GIT version? It should create
  valid
>OFXv1 requests now, however, I can't test it completely since
  I only
>have access to an OFXv2 server...
> 
> 
>Regards
>Martin
> 
> 
>Am 18.03.20 um 16:31 schrieb chris graves:
>> An additional bit of information from /tmp/ofx.log:
>> AQB5:
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318081757.000
>> 
>> ...
>[...]
> 
> 
>--
>"Things are only impossible until they're not"
> 
 
 
  -- 
  "Things are only impossible until they're not"
 
>>> 
>>> 
>>> -- 
>>> "Things are only impossible until they're not"
>> 
> 

___
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-Li

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

It actually requires make uninstall && make clean && make && make install to 
ensure that the changed code is used.

Regards,
John Ralls

> On Mar 18, 2020, at 2:52 PM, Martin Preuss  wrote:
> 
> Hi,
> 
> okay now, the latest GIT version always sets "OFXHEADER:100" and uses
> the given header version only for the "VERSION:" header. In that case
> you can specify "102" and it should create the correct headers...
> 
> Please note: For reasons not yet understood it might be necessary when
> updating from git to first issue "make clean" before "make", otherwise
> sometimes the resulting binaries might not be based on all the latest
> code (I have no idea whether this happens for others as well, it's just
> something I stumbled upon while working on AqBanking).
> 
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 22:47 schrieb John Ralls:
>> It won't let you leave that blank, and even if it did it would put '100' in 
>> both fields:
>> if (!(s && *s))
>>s="100";
>> 
>>  GWEN_Buffer_AppendString(buf, "OFXHEADER:");
>>  GWEN_Buffer_AppendString(buf, s);
>>  GWEN_Buffer_AppendString(buf, "\r\nDATA:OFXSGML\r\n");
>> 
>>  GWEN_Buffer_AppendString(buf, "VERSION:");
>>  s=AO_User_GetHeaderVer(u);
>>  if (!s || !*s)
>>s="102";
>>  GWEN_Buffer_AppendString(buf, s);
>>  GWEN_Buffer_AppendString(buf, "\r\n");
>> 
>> Because at the second test s has a value.
>> 
>> The new code doesn't emit the trailing tags, so that may not have been the 
>> problem. The main difference other than the OFXHEADER: value now appears to 
>> be that there are newlines between the fields. Are those getting escaped in 
>> GWEN_SyncIo_Http_Write?
>> 
>> Regards,
>> John Ralls
>>> On Mar 18, 2020, at 2:34 PM, Martin Preuss  wrote:
>>> 
>>> Hi,
>>> 
>>> not ATM, but that can be arranged. However, how about leaving that field
>>> empty in the settings dialog? That should default to 100 for OFXHEADER
>>> and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
>>> good^H^H^H reasons for those mixed defaults... :-})
>>> 
>>> Regards
>>> Martin
>>> 
>>> 
>>> Am 18.03.20 um 22:26 schrieb Chris Graves:
 Nice!  I see that the change has been made, but still receive the HTTP
 400 error.
 
 In the AQB5 ofx.log file for a successful case, I see
 OFXHEADER:100
 VERSION:102
 
 In the AQB6 file, I see
 OFXHEADER:102
 VERSION:102
 
 Not sure if this could be the problem.  Is there a way to set OFXHEADER
 and VERSION independently?
 
 
 On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >>> > wrote:
 
   Hi,
 
   you can change the header manually to 102/103 in the homebanking setup
   dialog (select user, edit user, switch to app settings and type-in
   header version 102).
 
   Regards
   Martin
 
 
   Am 18.03.20 um 21:57 schrieb Chris Graves:
> Hi Martin,
> 
> Looking better!  However, to my knowledge, my bank only supports OFX
> version 102 or 103.  I had been using 102.
> 
> ofx.log:
> Sending:
> -
> OFXHEADER:220
> DATA:OFXSGML
> VERSION:220
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318135033.000
> 
> 
> 
> 
> 20200318135025.000
> 
> On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss >>>   
> >> wrote:
> 
> Hi Chris,
> 
> could you please test the latest GIT version? It should create
   valid
> OFXv1 requests now, however, I can't test it completely since
   I only
> have access to an OFXv2 server...
> 
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 16:31 schrieb chris graves:
>> An additional bit of information from /tmp/ofx.log:
>> AQB5:
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318081757.000
>> 
>> ...
> [...]
> 
> 
> --
> "Things are only impossible until they're not"
> 
 
 
   -- 
   "Things are only impossible until they're not"
 
>>> 
>>> 
>>> -- 
>>> "Things are only impossible until they're not"
>> 
> 
> 
> -- 
> "Things are only impossible until they're not"

___
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 Re

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

Remember, the working ofx from AQB5 is
Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200315112517.000

20200315112517

ENGUSAA24591QWIN2300202003151125171202003140020200315112517Y


Regards,
John Ralls

> On Mar 18, 2020, at 2:54 PM, Martin Preuss  wrote:
> 
> Hi,
> 
> please see my other mail (latest GIT).
> 
> Maybe "103" then (I heard of some cases where "103" was necessary)? Or
> perhaps "160"?
> 
> Will fix the gui btw...
> 
> 
> Regards
> Martin
> 
> Am 18.03.20 um 22:50 schrieb Chris Graves:
>> Hi Martin,
>> 
>> The GUI wouldn't let me leave that field blank, so I manually deleted
>> the entry from the .conf file. Running again, it did use the defaults
>> that you specified.  However, still the http 400 error and no response.
>> 
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318144035.000
>> 
>> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss > > wrote:
>> 
>>Hi,
>> 
>>not ATM, but that can be arranged. However, how about leaving that field
>>empty in the settings dialog? That should default to 100 for OFXHEADER
>>and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
>>good^H^H^H reasons for those mixed defaults... :-})
>> 
>>Regards
>>Martin
>> 
>> 
>>Am 18.03.20 um 22:26 schrieb Chris Graves:
>>> Nice!  I see that the change has been made, but still receive the HTTP
>>> 400 error.
>>> 
>>> In the AQB5 ofx.log file for a successful case, I see
>>> OFXHEADER:100
>>> VERSION:102
>>> 
>>> In the AQB6 file, I see
>>> OFXHEADER:102
>>> VERSION:102
>>> 
>>> Not sure if this could be the problem.  Is there a way to set
>>OFXHEADER
>>> and VERSION independently?
>>> 
>>> 
>>> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >
>>> >> wrote:
>>> 
>>>  Hi,
>>> 
>>>  you can change the header manually to 102/103 in the
>>homebanking setup
>>>  dialog (select user, edit user, switch to app settings and type-in
>>>  header version 102).
>>> 
>>>  Regards
>>>  Martin
>>> 
>>> 
>>>  Am 18.03.20 um 21:57 schrieb Chris Graves:
>>>  > Hi Martin,
>>>  >
>>>  > Looking better!  However, to my knowledge, my bank only
>>supports OFX
>>>  > version 102 or 103.  I had been using 102.
>>>  >
>>>  > ofx.log:
>>>  > Sending:
>>>  > -
>>>  > OFXHEADER:220
>>>  > DATA:OFXSGML
>>>  > VERSION:220
>>>  > SECURITY:NONE
>>>  > ENCODING:USASCII
>>>  > CHARSET:1252
>>>  > COMPRESSION:NONE
>>>  > OLDFILEUID:NONE
>>>  > NEWFILEUID:20200318135033.000
>>>  >
>>>  > 
>>>  > 
>>>  > 
>>>  > 20200318135025.000
>>>  >
>>>  > On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss
>>mailto:mar...@aqbanking.de>
>>>  >
>>>  > 
>>>>  >
>>>  > Hi Chris,
>>>  >
>>>  > could you please test the latest GIT version? It should
>>create
>>>  valid
>>>  > OFXv1 requests now, however, I can't test it completely
>>since
>>>  I only
>>>  > have access to an OFXv2 server...
>>>  >
>>>  >
>>>  > Regards
>>>  > Martin
>>>  >
>>>  >
>>>  > Am 18.03.20 um 16:31 schrieb chris graves:
>>>  > > An additional bit of information from /tmp/ofx.log:
>>>  > > AQB5:
>>>  > > Sending:
>>>  > > -
>>>  > > OFXHEADER:100
>>>  > > DATA:OFXSGML
>>>  > > VERSION:102
>>>  > > SECURITY:NONE
>>>  > > ENCODING:USASCII
>>>  > > CHARSET:1252
>>>  > > COMPRESSION:NONE
>>>  > > OLDFILEUID:NONE
>>>  > > NEWFILEUID:20200318081757.000
>>>  > >
>>>  > > ...
>>>  > [...]
>>>  >
>>>  >
>>>  > --
>>>  > "Things are only impossible until they're not"
>>>  >
>>> 
>>> 
>>>  --
>>>  "Things are only impossible until they're not"
>>> 
>> 
>> 
>>-- 
>>"Things are only impossible until they're not"
>> 
> 
> 
> -- 
> "Things are only impossible until they're not"

___
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 informati

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

The only difference I see now in the ofx.logs is the newlines, and I still 
haven't figured out if they're correctly escaped in the http request.

Regards,
John Ralls


> On Mar 18, 2020, at 2:59 PM, Martin Preuss  wrote:
> 
> Hi again,
> 
> with the latest changes: Are there any probably important differences in
> the generated OFX request compared to Aqb5's output (except dates etc.)?
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 22:50 schrieb Chris Graves:
>> Hi Martin,
>> 
>> The GUI wouldn't let me leave that field blank, so I manually deleted
>> the entry from the .conf file. Running again, it did use the defaults
>> that you specified.  However, still the http 400 error and no response.
>> 
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318144035.000
>> 
>> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss > > wrote:
>> 
>>Hi,
>> 
>>not ATM, but that can be arranged. However, how about leaving that field
>>empty in the settings dialog? That should default to 100 for OFXHEADER
>>and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
>>good^H^H^H reasons for those mixed defaults... :-})
>> 
>>Regards
>>Martin
>> 
>> 
>>Am 18.03.20 um 22:26 schrieb Chris Graves:
>>> Nice!  I see that the change has been made, but still receive the HTTP
>>> 400 error.
>>> 
>>> In the AQB5 ofx.log file for a successful case, I see
>>> OFXHEADER:100
>>> VERSION:102
>>> 
>>> In the AQB6 file, I see
>>> OFXHEADER:102
>>> VERSION:102
>>> 
>>> Not sure if this could be the problem.  Is there a way to set
>>OFXHEADER
>>> and VERSION independently?
>>> 
>>> 
>>> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >
>>> >> wrote:
>>> 
>>>  Hi,
>>> 
>>>  you can change the header manually to 102/103 in the
>>homebanking setup
>>>  dialog (select user, edit user, switch to app settings and type-in
>>>  header version 102).
>>> 
>>>  Regards
>>>  Martin
>>> 
>>> 
>>>  Am 18.03.20 um 21:57 schrieb Chris Graves:
>>>  > Hi Martin,
>>>  >
>>>  > Looking better!  However, to my knowledge, my bank only
>>supports OFX
>>>  > version 102 or 103.  I had been using 102.
>>>  >
>>>  > ofx.log:
>>>  > Sending:
>>>  > -
>>>  > OFXHEADER:220
>>>  > DATA:OFXSGML
>>>  > VERSION:220
>>>  > SECURITY:NONE
>>>  > ENCODING:USASCII
>>>  > CHARSET:1252
>>>  > COMPRESSION:NONE
>>>  > OLDFILEUID:NONE
>>>  > NEWFILEUID:20200318135033.000
>>>  >
>>>  > 
>>>  > 
>>>  > 
>>>  > 20200318135025.000
>>>  >
>>>  > On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss
>>mailto:mar...@aqbanking.de>
>>>  >
>>>  > 
>>>>  >
>>>  > Hi Chris,
>>>  >
>>>  > could you please test the latest GIT version? It should
>>create
>>>  valid
>>>  > OFXv1 requests now, however, I can't test it completely
>>since
>>>  I only
>>>  > have access to an OFXv2 server...
>>>  >
>>>  >
>>>  > Regards
>>>  > Martin
>>>  >
>>>  >
>>>  > Am 18.03.20 um 16:31 schrieb chris graves:
>>>  > > An additional bit of information from /tmp/ofx.log:
>>>  > > AQB5:
>>>  > > Sending:
>>>  > > -
>>>  > > OFXHEADER:100
>>>  > > DATA:OFXSGML
>>>  > > VERSION:102
>>>  > > SECURITY:NONE
>>>  > > ENCODING:USASCII
>>>  > > CHARSET:1252
>>>  > > COMPRESSION:NONE
>>>  > > OLDFILEUID:NONE
>>>  > > NEWFILEUID:20200318081757.000
>>>  > >
>>>  > > ...
>>>  > [...]
>>>  >
>>>  >
>>>  > --
>>>  > "Things are only impossible until they're not"
>>>  >
>>> 
>>> 
>>>  --
>>>  "Things are only impossible until they're not"
>>> 
>> 
>> 
>>-- 
>>"Things are only impossible until they're not"
>> 
> 
> 
> -- 
> "Things are only impossible until they're not"

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[chris graves]

Is there any easy way to capture the dialog between the client and server?

> On Mar 18, 2020, at 3:04 PM, John Ralls  wrote:
> 
> The only difference I see now in the ofx.logs is the newlines, and I still 
> haven't figured out if they're correctly escaped in the http request.
> 
> Regards,
> John Ralls
> 
> 
>> On Mar 18, 2020, at 2:59 PM, Martin Preuss  wrote:
>> 
>> Hi again,
>> 
>> with the latest changes: Are there any probably important differences in
>> the generated OFX request compared to Aqb5's output (except dates etc.)?
>> 
>> Regards
>> Martin
>> 
>> 
>> Am 18.03.20 um 22:50 schrieb Chris Graves:
>>> Hi Martin,
>>> 
>>> The GUI wouldn't let me leave that field blank, so I manually deleted
>>> the entry from the .conf file. Running again, it did use the defaults
>>> that you specified.  However, still the http 400 error and no response.
>>> 
>>> Sending:
>>> -
>>> OFXHEADER:100
>>> DATA:OFXSGML
>>> VERSION:102
>>> SECURITY:NONE
>>> ENCODING:USASCII
>>> CHARSET:1252
>>> COMPRESSION:NONE
>>> OLDFILEUID:NONE
>>> NEWFILEUID:20200318144035.000
>>> 
>>> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss >> > wrote:
>>> 
>>>   Hi,
>>> 
>>>   not ATM, but that can be arranged. However, how about leaving that field
>>>   empty in the settings dialog? That should default to 100 for OFXHEADER
>>>   and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
>>>   good^H^H^H reasons for those mixed defaults... :-})
>>> 
>>>   Regards
>>>   Martin
>>> 
>>> 
>>>   Am 18.03.20 um 22:26 schrieb Chris Graves:
 Nice!  I see that the change has been made, but still receive the HTTP
 400 error.
 
 In the AQB5 ofx.log file for a successful case, I see
 OFXHEADER:100
 VERSION:102
 
 In the AQB6 file, I see
 OFXHEADER:102
 VERSION:102
 
 Not sure if this could be the problem.  Is there a way to set
>>>   OFXHEADER
 and VERSION independently?
 
 
 On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >>   
 >> wrote:
 
 Hi,
 
 you can change the header manually to 102/103 in the
>>>   homebanking setup
 dialog (select user, edit user, switch to app settings and type-in
 header version 102).
 
 Regards
 Martin
 
 
 Am 18.03.20 um 21:57 schrieb Chris Graves:
> Hi Martin,
> 
> Looking better!  However, to my knowledge, my bank only
>>>   supports OFX
> version 102 or 103.  I had been using 102.
> 
> ofx.log:
> Sending:
> -
> OFXHEADER:220
> DATA:OFXSGML
> VERSION:220
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318135033.000
> 
> 
> 
> 
> 20200318135025.000
> 
> On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss
>>>   mailto:mar...@aqbanking.de>
 >
> 
>>>    
>Hi Chris,
> 
>could you please test the latest GIT version? It should
>>>   create
 valid
>OFXv1 requests now, however, I can't test it completely
>>>   since
 I only
>have access to an OFXv2 server...
> 
> 
>Regards
>Martin
> 
> 
>Am 18.03.20 um 16:31 schrieb chris graves:
>> An additional bit of information from /tmp/ofx.log:
>> AQB5:
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318081757.000
>> 
>> ...
>[...]
> 
> 
>--
>"Things are only impossible until they're not"
> 
 
 
 --
 "Things are only impossible until they're not"
 
>>> 
>>> 
>>>   -- 
>>>   "Things are only impossible until they're not"
>>> 
>> 
>> 
>> -- 
>> "Things are only impossible until they're not"
> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hi,

hmm, so no linebreaks...

Could either of you please try with the following lines commented out in
v1/n_toofx.c:
- 105:   if (hasSubTags)
- 106: GWEN_Buffer_AppendString(buf, "\r\n");
- 128:   GWEN_Buffer_AppendString(buf, "\r\n");

Will be back in a few mins, have to watch an episode of "Bull" on my
wifes request... ;-)


Regards
Martin


Am 18.03.20 um 23:02 schrieb John Ralls:
> Remember, the working ofx from AQB5 is
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200315112517.000
> 
> 20200315112517
> 
> ENGUSAA24591QWIN2300202003151125171202003140020200315112517Y
> 
> 
> Regards,
> John Ralls
> 
>> On Mar 18, 2020, at 2:54 PM, Martin Preuss  wrote:
>>
>> Hi,
>>
>> please see my other mail (latest GIT).
>>
>> Maybe "103" then (I heard of some cases where "103" was necessary)? Or
>> perhaps "160"?
>>
>> Will fix the gui btw...
>>
>>
>> Regards
>> Martin
>>
>> Am 18.03.20 um 22:50 schrieb Chris Graves:
>>> Hi Martin,
>>>
>>> The GUI wouldn't let me leave that field blank, so I manually deleted
>>> the entry from the .conf file. Running again, it did use the defaults
>>> that you specified.  However, still the http 400 error and no response.
>>>
>>> Sending:
>>> -
>>> OFXHEADER:100
>>> DATA:OFXSGML
>>> VERSION:102
>>> SECURITY:NONE
>>> ENCODING:USASCII
>>> CHARSET:1252
>>> COMPRESSION:NONE
>>> OLDFILEUID:NONE
>>> NEWFILEUID:20200318144035.000
>>>
>>> On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss >> > wrote:
>>>
>>>Hi,
>>>
>>>not ATM, but that can be arranged. However, how about leaving that field
>>>empty in the settings dialog? That should default to 100 for OFXHEADER
>>>and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
>>>good^H^H^H reasons for those mixed defaults... :-})
>>>
>>>Regards
>>>Martin
>>>
>>>
>>>Am 18.03.20 um 22:26 schrieb Chris Graves:
 Nice!  I see that the change has been made, but still receive the HTTP
 400 error.

 In the AQB5 ofx.log file for a successful case, I see
 OFXHEADER:100
 VERSION:102

 In the AQB6 file, I see
 OFXHEADER:102
 VERSION:102

 Not sure if this could be the problem.  Is there a way to set
>>>OFXHEADER
 and VERSION independently?


 On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >>
 >> wrote:

  Hi,

  you can change the header manually to 102/103 in the
>>>homebanking setup
  dialog (select user, edit user, switch to app settings and type-in
  header version 102).

  Regards
  Martin


  Am 18.03.20 um 21:57 schrieb Chris Graves:
  > Hi Martin,
  >
  > Looking better!  However, to my knowledge, my bank only
>>>supports OFX
  > version 102 or 103.  I had been using 102.
  >
  > ofx.log:
  > Sending:
  > -
  > OFXHEADER:220
  > DATA:OFXSGML
  > VERSION:220
  > SECURITY:NONE
  > ENCODING:USASCII
  > CHARSET:1252
  > COMPRESSION:NONE
  > OLDFILEUID:NONE
  > NEWFILEUID:20200318135033.000
  >
  > 
  > 
  > 
  > 20200318135025.000
  >
  > On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss
>>>mailto:mar...@aqbanking.de>
  >
  > 
>>>
  > Hi Chris,
  >
  > could you please test the latest GIT version? It should
>>>create
  valid
  > OFXv1 requests now, however, I can't test it completely
>>>since
  I only
  > have access to an OFXv2 server...
  >
  >
  > Regards
  > Martin
  >
  >
  > Am 18.03.20 um 16:31 schrieb chris graves:
  > > An additional bit of information from /tmp/ofx.log:
  > > AQB5:
  > > Sending:
  > > -
  > > OFXHEADER:100
  > > DATA:OFXSGML
  > > VERSION:102
  > > SECURITY:NONE
  > > ENCODING:USASCII
  > > CHARSET:1252
  > > COMPRESSION:NONE
  > > OLDFILEUID:NONE
  > > NEWFILEUID:20200318081757.000
  > >
  > > ...
  > [...]
  >
  >
  > --
  > "Things are only impossible until they're no

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

Sigh, that's not it either:
Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318151247.000

2020031815124318015524376ENGUSAA24591QWIN23002020031815124724591427082906539504520200309002020031800Y

and a 400.

Regards,
John Ralls


> On Mar 18, 2020, at 3:08 PM, Martin Preuss  wrote:
> 
> Hi,
> 
> hmm, so no linebreaks...
> 
> Could either of you please try with the following lines commented out in
> v1/n_toofx.c:
> - 105:   if (hasSubTags)
> - 106: GWEN_Buffer_AppendString(buf, "\r\n");
> - 128:   GWEN_Buffer_AppendString(buf, "\r\n");
> 
> Will be back in a few mins, have to watch an episode of "Bull" on my
> wifes request... ;-)
> 
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 23:02 schrieb John Ralls:
>> Remember, the working ofx from AQB5 is
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200315112517.000
>> 
>> 20200315112517
>> 
>> ENGUSAA24591QWIN2300202003151125171202003140020200315112517Y
>> 
>> 
>> Regards,
>> John Ralls
>> 
>>> On Mar 18, 2020, at 2:54 PM, Martin Preuss  wrote:
>>> 
>>> Hi,
>>> 
>>> please see my other mail (latest GIT).
>>> 
>>> Maybe "103" then (I heard of some cases where "103" was necessary)? Or
>>> perhaps "160"?
>>> 
>>> Will fix the gui btw...
>>> 
>>> 
>>> Regards
>>> Martin
>>> 
>>> Am 18.03.20 um 22:50 schrieb Chris Graves:
 Hi Martin,
 
 The GUI wouldn't let me leave that field blank, so I manually deleted
 the entry from the .conf file. Running again, it did use the defaults
 that you specified.  However, still the http 400 error and no response.
 
 Sending:
 -
 OFXHEADER:100
 DATA:OFXSGML
 VERSION:102
 SECURITY:NONE
 ENCODING:USASCII
 CHARSET:1252
 COMPRESSION:NONE
 OLDFILEUID:NONE
 NEWFILEUID:20200318144035.000
 
 On Wed, Mar 18, 2020 at 2:34 PM Martin Preuss >>> > wrote:
 
   Hi,
 
   not ATM, but that can be arranged. However, how about leaving that field
   empty in the settings dialog? That should default to 100 for OFXHEADER
   and 102 for VERSION (for - ahem - historic reasons, I'm sure I had
   good^H^H^H reasons for those mixed defaults... :-})
 
   Regards
   Martin
 
 
   Am 18.03.20 um 22:26 schrieb Chris Graves:
> Nice!  I see that the change has been made, but still receive the HTTP
> 400 error.
> 
> In the AQB5 ofx.log file for a successful case, I see
> OFXHEADER:100
> VERSION:102
> 
> In the AQB6 file, I see
> OFXHEADER:102
> VERSION:102
> 
> Not sure if this could be the problem.  Is there a way to set
   OFXHEADER
> and VERSION independently?
> 
> 
> On Wed, Mar 18, 2020 at 2:02 PM Martin Preuss >>>   
> >> wrote:
> 
> Hi,
> 
> you can change the header manually to 102/103 in the
   homebanking setup
> dialog (select user, edit user, switch to app settings and type-in
> header version 102).
> 
> Regards
> Martin
> 
> 
> Am 18.03.20 um 21:57 schrieb Chris Graves:
>> Hi Martin,
>> 
>> Looking better!  However, to my knowledge, my bank only
   supports OFX
>> version 102 or 103.  I had been using 102.
>> 
>> ofx.log:
>> Sending:
>> -
>> OFXHEADER:220
>> DATA:OFXSGML
>> VERSION:220
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318135033.000
>> 
>> 
>> 
>> 
>> 20200318135025.000
>> 
>> On Wed, Mar 18, 2020 at 1:32 PM Martin Preuss
   mailto:mar...@aqbanking.de>
> >
>> 
   > 
>>Hi Chris,
>> 
>>could you please test the latest GIT version? It should
   create
> valid
>>OFXv1 requests now, however, I can't test it completely
   since
> I only
>>have access to an OFXv2 server...
>> 
>> 
>>Regards
>>Martin
>> 
>> 
>>Am 18.03.20 um 16:31 schrieb chris graves:
>>> An additional bit of information from /tmp/ofx.log:
>>> AQB5:
>>> Sending:
>>> -
>>> OFXHEADER:100
>>> DATA:OFXSGML
>>> VERSION:102
>>> SECURITY:NONE
>>> ENCODING:USASCII
>>> CHARSET:1252

Re: [GNC] General Ledger

[Michael or Penny Novack]

On 3/18/2020 1:52 PM, Stephen M. Butler wrote:

Adrian,

I give my CPA three items:

1.  Balance Sheet.

2.  Profit Loss statement

3.  Transaction Report of all transactions for the year sorted by
account and then by date within account.

That last is the "general ledger" (when for all accounts). As I noted 
earlier, the NAMES gnucash uses for reports can be confusing.  There 
isn't a way around this  in many cases because what some of these 
reports would be called depends on the type of entity. Thus the report 
named "Income Statement" would be called "Profit and Loss" if the entity 
is a for profit enterprise but "Statement of Revenues and Expenses" by 
an organization/non-profit.


Michael D Novack
___
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.

Re: [GNC] General Ledger

[Adrian Yong]

Thank you very much, Adrien, Michael and Stephen for helping me understand
Gnucash...

I will submit the documents as suggested by Stephen and see what the
auditors say... They are CPAs...







On Thu, 19 Mar. 2020, 06:37 Michael or Penny Novack, <
stepbystepf...@comcast.net> wrote:

> On 3/18/2020 1:52 PM, Stephen M. Butler wrote:
> > Adrian,
> >
> > I give my CPA three items:
> >
> > 1.  Balance Sheet.
> >
> > 2.  Profit Loss statement
> >
> > 3.  Transaction Report of all transactions for the year sorted by
> > account and then by date within account.
> >
> That last is the "general ledger" (when for all accounts). As I noted
> earlier, the NAMES gnucash uses for reports can be confusing.  There
> isn't a way around this  in many cases because what some of these
> reports would be called depends on the type of entity. Thus the report
> named "Income Statement" would be called "Profit and Loss" if the entity
> is a for profit enterprise but "Statement of Revenues and Expenses" by
> an organization/non-profit.
>
> Michael D Novack
> ___
> 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.
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hmm, maybe the server is picky about the HTTP version? Some servers
are... That can currently only be changed directly in the configuration
file:

$HOME/.aqbanking/settings6/users/*.conf

Some servers only accept httpVMinor="0"...


Regards
Martin



Am 18.03.20 um 23:20 schrieb John Ralls:
> Sigh, that's not it either:
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318151247.000
[...]

-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

That's what mine says:
char flags="forceSsl3", "sendShortDate"
char bankName="USAA Federal Savings Bank"
char org="USAA"
char fid="24591"
char serverAddr="https%3A%2F%2Fservice2.usaa.com%2Fofx%2FOFXServlet"
char appId="QWIN"
char appVer="2300"
char headerVer="102"
int  httpVMajor="0"
int  httpVMinor="0"
  }

Regards,
John Ralls


> On Mar 18, 2020, at 4:15 PM, Martin Preuss  wrote:
> 
> Hmm, maybe the server is picky about the HTTP version? Some servers
> are... That can currently only be changed directly in the configuration
> file:
> 
> $HOME/.aqbanking/settings6/users/*.conf
> 
> Some servers only accept httpVMinor="0"...
> 
> 
> Regards
> Martin
> 
> 
> 
> Am 18.03.20 um 23:20 schrieb John Ralls:
>> Sigh, that's not it either:
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318151247.000
> [...]
> 
> -- 
> "Things are only impossible until they're not"

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Hi,

I just checked in another change... While comparing your logs I found
that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".

Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).

Also, I noticed that aqb5 included "BANKID" which you log from aqb6
didn't contain that line...

However, I think the unexpected element "LANG" (instead of "LANGUAGE")
was what made the server reject the request due to syntax error...

Fixed in git.


Regards
Martin


Am 19.03.20 um 00:26 schrieb John Ralls:
> That's what mine says:
> char flags="forceSsl3", "sendShortDate"
> char bankName="USAA Federal Savings Bank"
> char org="USAA"
> char fid="24591"
> char serverAddr="https%3A%2F%2Fservice2.usaa.com%2Fofx%2FOFXServlet"
> char appId="QWIN"
> char appVer="2300"
> char headerVer="102"
> int  httpVMajor="0"
> int  httpVMinor="0"
>   }
> 
> Regards,
> John Ralls
> 
> 
>> On Mar 18, 2020, at 4:15 PM, Martin Preuss  wrote:
>>
>> Hmm, maybe the server is picky about the HTTP version? Some servers
>> are... That can currently only be changed directly in the configuration
>> file:
>>
>> $HOME/.aqbanking/settings6/users/*.conf
>>
>> Some servers only accept httpVMinor="0"...
>>
>>
>> Regards
>> Martin
>>
>>
>>
>> Am 18.03.20 um 23:20 schrieb John Ralls:
>>> Sigh, that's not it either:
>>> Sending:
>>> -
>>> OFXHEADER:100
>>> DATA:OFXSGML
>>> VERSION:102
>>> SECURITY:NONE
>>> ENCODING:USASCII
>>> CHARSET:1252
>>> COMPRESSION:NONE
>>> OLDFILEUID:NONE
>>> NEWFILEUID:20200318151247.000
>> [...]
>>
>> -- 
>> "Things are only impossible until they're not"
> 


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

I did
--- a/src/libs/plugins/backends/aqofxconnect/v1/r_statements.c
+++ b/src/libs/plugins/backends/aqofxconnect/v1/r_statements.c
@@ -77,7 +77,7 @@ int AO_V1_RequestStatements(AB_PROVIDER *pro, AB_USER *u, 
AB_ACCOUNT *a, AB_TRAN
   }
   GWEN_XMLNode_free(xmlRoot);

-#if 0
+#if 1
   DBG_ERROR(AQOFXCONNECT_LOGDOMAIN, "OFX request:");
   fprintf(stderr, "%s\n", GWEN_Buffer_GetStart(bufRequest));
   GWEN_Text_LogString(GWEN_Buffer_GetStart(bufRequest),
@@ -99,7 +99,7 @@ int AO_V1_RequestStatements(AB_PROVIDER *pro, AB_USER *u, 
AB_ACCOUNT *a, AB_TRAN
   GWEN_Buffer_free(bufRequest);


-#if 0
+#if 1
   DBG_ERROR(AQOFXCONNECT_LOGDOMAIN, "OFX response:");
   GWEN_Text_LogString(GWEN_Buffer_GetStart(bufResponse),
   GWEN_Buffer_GetUsedBytes(bufResponse),

to get some more out of the logs. That inserted the exact same string as in 
ofx.log, which is good, but with GWEN_LOGLEVEL=debug the next bit of the log is
* 15:22:21 ERROR  io_network.c:  165: Saving OFX log to 
"/tmp/ofx.log" ...
7:2020/03/18 
15-22-21:gwen(83151):/Users/john/Development/Gnucash-Build/Gnucash-3/src/gwenhywfar-5.2.0/src/parser/urlfns.c:
  123: Server: [service2.usaa.com]
7:2020/03/18 
15-22-21:gwen(83151):/Users/john/Development/Gnucash-Build/Gnucash-3/src/gwenhywfar-5.2.0/src/parser/urlfns.c:
  176: Path: [/ofx/OFXServlet]
7:2020/03/18 
15-22-21:gwen(83151):/Users/john/Development/Gnucash-Build/Gnucash-3/src/gwenhywfar-5.2.0/src/parser/urlfns.c:
  123: Server: [service2.usaa.com]
7:2020/03/18 
15-22-21:gwen(83151):/Users/john/Development/Gnucash-Build/Gnucash-3/src/gwenhywfar-5.2.0/src/parser/urlfns.c:
  176: Path: [/ofx/OFXServlet]
7:2020/03/18 15-22-21:gwen(83151):String size is 31
7:2020/03/18 15-22-21:gwen(83151):: 50 4f 53 54 20 2f 6f 66 78 2f 4f 46 58 
53 65 72 POST /ofx/OFXSer
7:2020/03/18 15-22-21:gwen(83151):0010: 76 6c 65 74 20 48 54 54 50 2f 31 2e 30 
0d 0avlet HTTP/1.0..
7:2020/03/18 15-22-21:gwen(83151):String size is 159
7:2020/03/18 15-22-21:gwen(83151):: 48 6f 73 74 3a 73 65 72 76 69 63 65 32 
2e 75 73 Host:service2.us
7:2020/03/18 15-22-21:gwen(83151):0010: 61 61 2e 63 6f 6d 0d 0a 43 6f 6e 6e 65 
63 74 69 aa.com..Connecti
7:2020/03/18 15-22-21:gwen(83151):0020: 6f 6e 3a 63 6c 6f 73 65 0d 0a 50 72 61 
67 6d 61 on:close..Pragma
7:2020/03/18 15-22-21:gwen(83151):0030: 3a 6e 6f 2d 63 61 63 68 65 0d 0a 43 61 
63 68 65 :no-cache..Cache
7:2020/03/18 15-22-21:gwen(83151):0040: 2d 63 6f 6e 74 72 6f 6c 3a 6e 6f 20 63 
61 63 68 -control:no cach
7:2020/03/18 15-22-21:gwen(83151):0050: 65 0d 0a 43 6f 6e 74 65 6e 74 2d 74 79 
70 65 3a e..Content-type:
7:2020/03/18 15-22-21:gwen(83151):0060: 61 70 70 6c 69 63 61 74 69 6f 6e 2f 78 
2d 6f 66 application/x-of
7:2020/03/18 15-22-21:gwen(83151):0070: 78 0d 0a 55 73 65 72 2d 41 67 65 6e 74 
3a 41 71 x..User-Agent:Aq
7:2020/03/18 15-22-21:gwen(83151):0080: 42 61 6e 6b 69 6e 67 0d 0a 43 6f 6e 74 
65 6e 74 Banking..Content
7:2020/03/18 15-22-21:gwen(83151):0090: 2d 6c 65 6e 67 74 68 3a 35 37 35 0d 0a 
0d 0a-length:575
7:2020/03/18 15-22-21:gwen(83151):String size is 25
7:2020/03/18 15-22-21:gwen(83151):: 48 54 54 50 2f 31 2e 30 20 34 30 30 20 
42 61 64 HTTP/1.0 400 Bad
7:2020/03/18 15-22-21:gwen(83151):0010: 20 52 65 71 75 65 73 74 00  
 Request.
:

Should there be two \n\r after the length header and is it supposed to log the 
request content? Unfortunately Gwen4 doesn't emit anything useful for 
comparison.

Regards,
John Ralls

> On Mar 18, 2020, at 3:20 PM, John Ralls  wrote:
> 
> Sigh, that's not it either:
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318151247.000
> 
> 20200318151243XXENGUSAA24591QWIN23002020031815124724591XXX20200309002020031800Y
> 
> and a 400.
> 
> Regards,
> John Ralls
> 
> 
>> On Mar 18, 2020, at 3:08 PM, Martin Preuss  wrote:
>> 
>> Hi,
>> 
>> hmm, so no linebreaks...
>> 
>> Could either of you please try with the following lines commented out in
>> v1/n_toofx.c:
>> - 105:   if (hasSubTags)
>> - 106: GWEN_Buffer_AppendString(buf, "\r\n");
>> - 128:   GWEN_Buffer_AppendString(buf, "\r\n");
>> 
>> Will be back in a few mins, have to watch an episode of "Bull" on my
>> wifes request... ;-)
>> 
>> 
>> Regards
>> Martin
>> 
>> 
>> Am 18.03.20 um 23:02 schrieb John Ralls:
>>> Remember, the working ofx from AQB5 is
>>> Sending:
>>> -
>>> OFXHEADER:100
>>> DATA:OFXSGML
>>> VERSION:102
>>> SECURITY:NONE
>>> ENCODING:USASCII
>>> CHARSET:1252
>>> COMPRESSION:NONE
>>> OLDFILEUID:NONE
>>> NEWFILEUID:20200315112517.000
>>> 
>>> 20200315112517
>>> 
>>> ENGUSAA24591QWIN2300202003151125171202003140020200315112517Y
>>> 
>>> 
>>> Regards,
>>> John Ralls
>>> 
 On Mar 18, 2020, at 2:54 PM, Martin Preuss  wrote:
 
 Hi,
 
 please see my other mail (latest GI

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

the OFX specs show this example:

-X8
POST http://www.fi.com/ofx.cgi HTTP/1.0
User-Agent:MyApp 5.0
Content-Type: application/x-ofx
Content-Length: 1032

OFXHEADER:100
DATA:OFXSGML
VERSION:160
SECURITY:TYPE1
ENCODING:USASCII
CHARSET:NONE
COMPRESSION:NONE
NEWFILEUID:NONE
OLDFILEUID:NONE


... Open Financial Exchange requests ...

-X8

or, in a table:

-X8
HTTP headers
CRLF(s)
MIME type information
CRLF(s)
OFX header element 1
CRLF
OFX header element 2
CRLF
OFX header element n
CRLF(s)
OFX SGML Block
-X8

Well, the table isn't that helpfull...
But the specs also state that all elements - http headers, OFX headers
and OFX request - should be separated by a blank line from each other...


Regards
Martin



-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

Wow! making serious progress now.  I was requesting transactions from my
checking account.  Looking at the ofx.log file, they were returned!!!

However the import process indicated that there were no transactions to be
imported.

On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss  wrote:

> Hi,
>
> I just checked in another change... While comparing your logs I found
> that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
>
> Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
>
> Also, I noticed that aqb5 included "BANKID" which you log from aqb6
> didn't contain that line...
>
> However, I think the unexpected element "LANG" (instead of "LANGUAGE")
> was what made the server reject the request due to syntax error...
>
> Fixed in git.
>
>
> Regards
> Martin
>
>
> Am 19.03.20 um 00:26 schrieb John Ralls:
> > That's what mine says:
> > char flags="forceSsl3", "sendShortDate"
> > char bankName="USAA Federal Savings Bank"
> > char org="USAA"
> > char fid="24591"
> > char serverAddr="https%3A%2F%2Fservice2.usaa.com%2Fofx%2FOFXServlet"
> > char appId="QWIN"
> > char appVer="2300"
> > char headerVer="102"
> > int  httpVMajor="0"
> > int  httpVMinor="0"
> >   }
> >
> > Regards,
> > John Ralls
> >
> >
> >> On Mar 18, 2020, at 4:15 PM, Martin Preuss  wrote:
> >>
> >> Hmm, maybe the server is picky about the HTTP version? Some servers
> >> are... That can currently only be changed directly in the configuration
> >> file:
> >>
> >> $HOME/.aqbanking/settings6/users/*.conf
> >>
> >> Some servers only accept httpVMinor="0"...
> >>
> >>
> >> Regards
> >> Martin
> >>
> >>
> >>
> >> Am 18.03.20 um 23:20 schrieb John Ralls:
> >>> Sigh, that's not it either:
> >>> Sending:
> >>> -
> >>> OFXHEADER:100
> >>> DATA:OFXSGML
> >>> VERSION:102
> >>> SECURITY:NONE
> >>> ENCODING:USASCII
> >>> CHARSET:1252
> >>> COMPRESSION:NONE
> >>> OLDFILEUID:NONE
> >>> NEWFILEUID:20200318151247.000
> >> [...]
> >>
> >> --
> >> "Things are only impossible until they're not"
> >
>
>
> --
> "Things are only impossible until they're not"
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

Nope:
Connected.
Sending message...
Message sent.
Waiting for response...
Receiving response...
HTTP-Status: 400 (Bad Request)
Unlocking customer "8"

Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318164314.000




20200318164310


ENG

USAA
24591

QWIN
2300




20200318164314
1


24591
XX


2020030900
2020031800
Y






Taking out the \r\n's doesn't help either.

Regards,
John Ralls

> On Mar 18, 2020, at 4:32 PM, Martin Preuss  wrote:
> 
> Hi,
> 
> I just checked in another change... While comparing your logs I found
> that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
> 
> Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
> 
> Also, I noticed that aqb5 included "BANKID" which you log from aqb6
> didn't contain that line...
> 
> However, I think the unexpected element "LANG" (instead of "LANGUAGE")
> was what made the server reject the request due to syntax error...
> 
> Fixed in git.
> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

Progress indeed, though still not enough for USAA. :-(

Regards,
John Ralls


> On Mar 18, 2020, at 4:48 PM, Chris Graves  wrote:
> 
> Wow! making serious progress now.  I was requesting transactions from my 
> checking account.  Looking at the ofx.log file, they were returned!!!
> 
> However the import process indicated that there were no transactions to be 
> imported.
> 
> On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss  wrote:
> Hi,
> 
> I just checked in another change... While comparing your logs I found
> that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
> 
> Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
> 
> Also, I noticed that aqb5 included "BANKID" which you log from aqb6
> didn't contain that line...
> 
> However, I think the unexpected element "LANG" (instead of "LANGUAGE")
> was what made the server reject the request due to syntax error...
> 
> Fixed in git.
> 
> 
> Regards
> Martin
> 
> 
> Am 19.03.20 um 00:26 schrieb John Ralls:
> > That's what mine says:
> > char flags="forceSsl3", "sendShortDate"
> > char bankName="USAA Federal Savings Bank"
> > char org="USAA"
> > char fid="24591"
> > char serverAddr="https%3A%2F%2Fservice2.usaa.com%2Fofx%2FOFXServlet"
> > char appId="QWIN"
> > char appVer="2300"
> > char headerVer="102"
> > int  httpVMajor="0"
> > int  httpVMinor="0"
> >   }
> > 
> > Regards,
> > John Ralls
> > 
> > 
> >> On Mar 18, 2020, at 4:15 PM, Martin Preuss  wrote:
> >>
> >> Hmm, maybe the server is picky about the HTTP version? Some servers
> >> are... That can currently only be changed directly in the configuration
> >> file:
> >>
> >> $HOME/.aqbanking/settings6/users/*.conf
> >>
> >> Some servers only accept httpVMinor="0"...
> >>
> >>
> >> Regards
> >> Martin
> >>
> >>
> >>
> >> Am 18.03.20 um 23:20 schrieb John Ralls:
> >>> Sigh, that's not it either:
> >>> Sending:
> >>> -
> >>> OFXHEADER:100
> >>> DATA:OFXSGML
> >>> VERSION:102
> >>> SECURITY:NONE
> >>> ENCODING:USASCII
> >>> CHARSET:1252
> >>> COMPRESSION:NONE
> >>> OLDFILEUID:NONE
> >>> NEWFILEUID:20200318151247.000
> >> [...]
> >>
> >> -- 
> >> "Things are only impossible until they're not"
> > 
> 
> 
> -- 
> "Things are only impossible until they're not"

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

Interesting, there were 8 Sending requests and 3 Received responses.  Looks
like transactions were returned duplicated 3 times.

On Wed, Mar 18, 2020 at 4:46 PM Martin Preuss  wrote:

>
> the OFX specs show this example:
>
> -X8
> POST http://www.fi.com/ofx.cgi HTTP/1.0
> User-Agent:MyApp 5.0
> Content-Type: application/x-ofx
> Content-Length: 1032
>
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:160
> SECURITY:TYPE1
> ENCODING:USASCII
> CHARSET:NONE
> COMPRESSION:NONE
> NEWFILEUID:NONE
> OLDFILEUID:NONE
>
> 
> ... Open Financial Exchange requests ...
> 
> -X8
>
> or, in a table:
>
> -X8
> HTTP headers
> CRLF(s)
> MIME type information
> CRLF(s)
> OFX header element 1
> CRLF
> OFX header element 2
> CRLF
> OFX header element n
> CRLF(s)
> OFX SGML Block
> -X8
>
> Well, the table isn't that helpfull...
> But the specs also state that all elements - http headers, OFX headers
> and OFX request - should be separated by a blank line from each other...
>
>
> Regards
> Martin
>
>
>
> --
> "Things are only impossible until they're not"
> ___
> 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.
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

Okay, we should now look for console logs.
I'm not sure how Gnucash handles log files, but you could try the
process of requesting statements using console-only:


1. get list of accounts:
# aqbanking-cli listaccounts
Column 6 contains the unique account id to be used in the next step.

2. get statements for an account with debug output
# AQOFXCONNECT_LOGLEVEL=info aqbanking-cli request --aid=UNIQUEID
--transactions --fromdate=20200301
-c OUTPUTFILE.ctx

3. Look into the file OUTPUTFILE.ctx: Does it contain transactions? If
not: Is there any helpfull output on the console?


Regards
Martin


Am 19.03.20 um 00:48 schrieb Chris Graves:
> Wow! making serious progress now.  I was requesting transactions from my
> checking account.  Looking at the ofx.log file, they were returned!!!
> 
> However the import process indicated that there were no transactions to
> be imported.
[...]

-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

John,

In your ofx.log file it still says LANGUAGE instead of LANG.  Mine says
LANG, which is what Martin just fixed.

On Wed, Mar 18, 2020 at 4:54 PM John Ralls  wrote:

> Progress indeed, though still not enough for USAA. :-(
>
> Regards,
> John Ralls
>
>
> > On Mar 18, 2020, at 4:48 PM, Chris Graves  wrote:
> >
> > Wow! making serious progress now.  I was requesting transactions from my
> checking account.  Looking at the ofx.log file, they were returned!!!
> >
> > However the import process indicated that there were no transactions to
> be imported.
> >
> > On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss 
> wrote:
> > Hi,
> >
> > I just checked in another change... While comparing your logs I found
> > that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
> >
> > Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
> >
> > Also, I noticed that aqb5 included "BANKID" which you log from aqb6
> > didn't contain that line...
> >
> > However, I think the unexpected element "LANG" (instead of "LANGUAGE")
> > was what made the server reject the request due to syntax error...
> >
> > Fixed in git.
> >
> >
> > Regards
> > Martin
> >
> >
> > Am 19.03.20 um 00:26 schrieb John Ralls:
> > > That's what mine says:
> > > char flags="forceSsl3", "sendShortDate"
> > > char bankName="USAA Federal Savings Bank"
> > > char org="USAA"
> > > char fid="24591"
> > > char serverAddr="https%3A%2F%2Fservice2.usaa.com
> %2Fofx%2FOFXServlet"
> > > char appId="QWIN"
> > > char appVer="2300"
> > > char headerVer="102"
> > > int  httpVMajor="0"
> > > int  httpVMinor="0"
> > >   }
> > >
> > > Regards,
> > > John Ralls
> > >
> > >
> > >> On Mar 18, 2020, at 4:15 PM, Martin Preuss 
> wrote:
> > >>
> > >> Hmm, maybe the server is picky about the HTTP version? Some servers
> > >> are... That can currently only be changed directly in the
> configuration
> > >> file:
> > >>
> > >> $HOME/.aqbanking/settings6/users/*.conf
> > >>
> > >> Some servers only accept httpVMinor="0"...
> > >>
> > >>
> > >> Regards
> > >> Martin
> > >>
> > >>
> > >>
> > >> Am 18.03.20 um 23:20 schrieb John Ralls:
> > >>> Sigh, that's not it either:
> > >>> Sending:
> > >>> -
> > >>> OFXHEADER:100
> > >>> DATA:OFXSGML
> > >>> VERSION:102
> > >>> SECURITY:NONE
> > >>> ENCODING:USASCII
> > >>> CHARSET:1252
> > >>> COMPRESSION:NONE
> > >>> OLDFILEUID:NONE
> > >>> NEWFILEUID:20200318151247.000
> > >> [...]
> > >>
> > >> --
> > >> "Things are only impossible until they're not"
> > >
> >
> >
> > --
> > "Things are only impossible until they're not"
>
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

I changed aqb6 to use "LANGUAGE" like aqb5 did, because that is the
correct name (don't know where I read "LANG", I guess that was in
another protocol...)

According to the specs (1.6) "LANGUAGE" should be used.


Regards
Martin



Am 19.03.20 um 00:57 schrieb Chris Graves:
> John,
> 
> In your ofx.log file it still says LANGUAGE instead of LANG.  Mine says
> LANG, which is what Martin just fixed.
> 
> On Wed, Mar 18, 2020 at 4:54 PM John Ralls  > wrote:
> 
> Progress indeed, though still not enough for USAA. :-(
> 
> Regards,
> John Ralls
> 
> 
> > On Mar 18, 2020, at 4:48 PM, Chris Graves  > wrote:
> >
> > Wow! making serious progress now.  I was requesting transactions
> from my checking account.  Looking at the ofx.log file, they were
> returned!!!
> >
> > However the import process indicated that there were no
> transactions to be imported.
> >
> > On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss  > wrote:
> > Hi,
> >
> > I just checked in another change... While comparing your logs I found
> > that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
> >
> > Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
> >
> > Also, I noticed that aqb5 included "BANKID" which you log from aqb6
> > didn't contain that line...
> >
> > However, I think the unexpected element "LANG" (instead of "LANGUAGE")
> > was what made the server reject the request due to syntax error...
> >
> > Fixed in git.
> >
> >
> > Regards
> > Martin
> >
> >
> > Am 19.03.20 um 00:26 schrieb John Ralls:
> > > That's what mine says:
> > >     char flags="forceSsl3", "sendShortDate"
> > >     char bankName="USAA Federal Savings Bank"
> > >     char org="USAA"
> > >     char fid="24591"
> > >     char serverAddr="https%3A%2F%2Fservice2.usaa.com
> %2Fofx%2FOFXServlet"
> > >     char appId="QWIN"
> > >     char appVer="2300"
> > >     char headerVer="102"
> > >     int  httpVMajor="0"
> > >     int  httpVMinor="0"
> > >   }
> > >
> > > Regards,
> > > John Ralls
> > >
> > >
> > >> On Mar 18, 2020, at 4:15 PM, Martin Preuss  > wrote:
> > >>
> > >> Hmm, maybe the server is picky about the HTTP version? Some servers
> > >> are... That can currently only be changed directly in the
> configuration
> > >> file:
> > >>
> > >> $HOME/.aqbanking/settings6/users/*.conf
> > >>
> > >> Some servers only accept httpVMinor="0"...
> > >>
> > >>
> > >> Regards
> > >> Martin
> > >>
> > >>
> > >>
> > >> Am 18.03.20 um 23:20 schrieb John Ralls:
> > >>> Sigh, that's not it either:
> > >>> Sending:
> > >>> -
> > >>> OFXHEADER:100
> > >>> DATA:OFXSGML
> > >>> VERSION:102
> > >>> SECURITY:NONE
> > >>> ENCODING:USASCII
> > >>> CHARSET:1252
> > >>> COMPRESSION:NONE
> > >>> OLDFILEUID:NONE
> > >>> NEWFILEUID:20200318151247.000
> > >> [...]
> > >>
> > >> --
> > >> "Things are only impossible until they're not"
> > >
> >
> >
> > --
> > "Things are only impossible until they're not"
> 


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Martin Preuss]

So the only remaining difference is the line "bankid" which wasn't in
the aqb5 log.

Just applied a change to the git repository to change that...


Regards
Martin


Am 19.03.20 um 00:53 schrieb John Ralls:
> Nope:
> Connected.
> Sending message...
> Message sent.
> Waiting for response...
> Receiving response...
> HTTP-Status: 400 (Bad Request)
> Unlocking customer "8"
> 
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318164314.000
> 
> 
> 
> 
> 20200318164310
> 
> 
> ENG
> 
> USAA
> 24591
> 
> QWIN
> 2300
> 
> 
> 
> 
> 20200318164314
> 1
> 
> 
> 24591
> XX
> 
> 
> 2020030900
> 2020031800
> Y
> 
> 
> 
> 
> 
> 
> Taking out the \r\n's doesn't help either.
> 
> Regards,
> John Ralls
> 
>> On Mar 18, 2020, at 4:32 PM, Martin Preuss  wrote:
>>
>> Hi,
>>
>> I just checked in another change... While comparing your logs I found
>> that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
>>
>> Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
>>
>> Also, I noticed that aqb5 included "BANKID" which you log from aqb6
>> didn't contain that line...
>>
>> However, I think the unexpected element "LANG" (instead of "LANGUAGE")
>> was what made the server reject the request due to syntax error...
>>
>> Fixed in git.
>>
> 


-- 
"Things are only impossible until they're not"
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

Chris,

You have it backwards: Martin changed LANG -> LANGUAGE because that's what AQB5 
used.

However, I just tested on a bank account at USAA and that worked, except that 
it crashed GnuCash when trying to process the new transactions. That's probably 
not AQBanking's doing and I'll look into that separately.

Next I'll try Martin's command-line test.

Regards,
John Ralls


> On Mar 18, 2020, at 4:57 PM, Chris Graves  wrote:
> 
> John,
> 
> In your ofx.log file it still says LANGUAGE instead of LANG.  Mine says LANG, 
> which is what Martin just fixed.
> 
> On Wed, Mar 18, 2020 at 4:54 PM John Ralls  wrote:
> Progress indeed, though still not enough for USAA. :-(
> 
> Regards,
> John Ralls
> 
> 
> > On Mar 18, 2020, at 4:48 PM, Chris Graves  wrote:
> > 
> > Wow! making serious progress now.  I was requesting transactions from my 
> > checking account.  Looking at the ofx.log file, they were returned!!!
> > 
> > However the import process indicated that there were no transactions to be 
> > imported.
> > 
> > On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss  wrote:
> > Hi,
> > 
> > I just checked in another change... While comparing your logs I found
> > that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
> > 
> > Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
> > 
> > Also, I noticed that aqb5 included "BANKID" which you log from aqb6
> > didn't contain that line...
> > 
> > However, I think the unexpected element "LANG" (instead of "LANGUAGE")
> > was what made the server reject the request due to syntax error...
> > 
> > Fixed in git.
> > 
> > 
> > Regards
> > Martin
> > 
> > 
> > Am 19.03.20 um 00:26 schrieb John Ralls:
> > > That's what mine says:
> > > char flags="forceSsl3", "sendShortDate"
> > > char bankName="USAA Federal Savings Bank"
> > > char org="USAA"
> > > char fid="24591"
> > > char serverAddr="https%3A%2F%2Fservice2.usaa.com%2Fofx%2FOFXServlet"
> > > char appId="QWIN"
> > > char appVer="2300"
> > > char headerVer="102"
> > > int  httpVMajor="0"
> > > int  httpVMinor="0"
> > >   }
> > > 
> > > Regards,
> > > John Ralls
> > > 
> > > 
> > >> On Mar 18, 2020, at 4:15 PM, Martin Preuss  wrote:
> > >>
> > >> Hmm, maybe the server is picky about the HTTP version? Some servers
> > >> are... That can currently only be changed directly in the configuration
> > >> file:
> > >>
> > >> $HOME/.aqbanking/settings6/users/*.conf
> > >>
> > >> Some servers only accept httpVMinor="0"...
> > >>
> > >>
> > >> Regards
> > >> Martin
> > >>
> > >>
> > >>
> > >> Am 18.03.20 um 23:20 schrieb John Ralls:
> > >>> Sigh, that's not it either:
> > >>> Sending:
> > >>> -
> > >>> OFXHEADER:100
> > >>> DATA:OFXSGML
> > >>> VERSION:102
> > >>> SECURITY:NONE
> > >>> ENCODING:USASCII
> > >>> CHARSET:1252
> > >>> COMPRESSION:NONE
> > >>> OLDFILEUID:NONE
> > >>> NEWFILEUID:20200318151247.000
> > >> [...]
> > >>
> > >> -- 
> > >> "Things are only impossible until they're not"
> > > 
> > 
> > 
> > -- 
> > "Things are only impossible until they're not"
> 

___
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.

Re: [GNC] credit card split transactions

[Adrien Monteleone]

First, please always copy the list on all replies - others may benefit from the 
discussion or lend better advice.

-

As for using a Check vs. a Credit Card for payment, there’s no difference 
between them.

Say you make a purchase at a store for bottled water and batteries with cash, 
this would be your sample transaction:

Dr. Expenses:Household  $5
Dr. Expenses:Food   $5
Cr. Assets:Cash $10

If you paid with a check or debit card tied to your checking account then:

Dr. Expenses:Household  $5
Dr. Expenses:Food   $5
Cr. Assets:Checking $10

If you paid with a credit card, then:

Dr. Expenses:Household  $5
Dr. Expenses:Food   $5
Cr. Liabilities:CreditCard  $10

They are all the same transaction in form, with the difference being the source 
of funds.

If you aren’t using formal accounting labels (Preferences > Accounts > Labels) 
then you will see “Total Payments” and “Total Charges” as your column headings, 
but that is really just “Total Debit” and “Total Credit” respectively. The same 
amounts go in the same columns regardless of if the labels are formal or not. 
(I don’t particularly care for the informal labels because they don’t really 
apply to both sides of credit transactions and find them much more confusing 
than ‘debit’ and ‘credit’.)

If this isn’t what you’re trying to accomplish, provide an example like one of 
those above and we’ll try to help further.

Regards,
Adrien

> On Mar 18, 2020 w12d78, at 5:18 PM, Jim Spalding 
>  wrote:
> 
> I am referring to credit card transactions with multiple splits. I was able 
> to understand the checking account multiple split directions, but not the 
> credit card transaction with more than two splits. 
> 
> On Tue, Mar 17, 2020 at 3:52 PM Adrien Monteleone 
>  wrote:
> Note, *all* transactions are ’split’ between at least two accounts. That is 
> the nature of double-entry. You may have more than two splits however 
> depending on the transaction.
> 
> The Help and Tutorial and Concepts Guides are a good place to start. I 
> wouldn’t attempt any further use of GnuCash without one or both of those 
> documents open and handy for reference as you learn the app.
> 
> What specifically are you finding difficult? Is this a charge to the card, an 
> interest or other account fee, or a payment that you are trying to enter?
> 
> Regards,
> Adrien
> 
> > On Mar 17, 2020 w12d77, at 2:14 PM, Jim Spalding 
> >  wrote:
> > 
> > Thanks in advance for your help. I have attempted - for a couple of hours -
> > to understand how to enter a split credit card transaction. Am I
> > overlooking a tutorial someplace? If so, I would really appreciate a link
> > to the tutorial.
> > 
> > Thanks,
> > Jim Spalding

___
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.

Re: [GNC] General Ledger

[Adrien Monteleone]

If they find info is missing or they don’t care for the formats, report back 
here and we’ll try to help you refine them.

Regards,
Adrien

> On Mar 18, 2020 w12d78, at 6:01 PM, Adrian Yong  
> wrote:
> 
> Thank you very much, Adrien, Michael and Stephen for helping me understand
> Gnucash...
> 
> I will submit the documents as suggested by Stephen and see what the
> auditors say... They are CPAs...

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

That did it!

Now to that crash.

Regards,
John Ralls

> On Mar 18, 2020, at 5:06 PM, Martin Preuss  wrote:
> 
> So the only remaining difference is the line "bankid" which wasn't in
> the aqb5 log.
> 
> Just applied a change to the git repository to change that...
> 
> 
> Regards
> Martin
> 
> 
> Am 19.03.20 um 00:53 schrieb John Ralls:
>> Nope:
>> Connected.
>> Sending message...
>> Message sent.
>> Waiting for response...
>> Receiving response...
>> HTTP-Status: 400 (Bad Request)
>> Unlocking customer "8"
>> 
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318164314.000
>> 
>> 
>> 
>> 
>> 20200318164310
>> 
>> 
>> ENG
>> 
>> USAA
>> 24591
>> 
>> QWIN
>> 2300
>> 
>> 
>> 
>> 
>> 20200318164314
>> 1
>> 
>> 
>> 24591
>> XX
>> 
>> 
>> 2020030900
>> 2020031800
>> Y
>> 
>> 
>> 
>> 
>> 
>> 
>> Taking out the \r\n's doesn't help either.
>> 
>> Regards,
>> John Ralls
>> 
>>> On Mar 18, 2020, at 4:32 PM, Martin Preuss  wrote:
>>> 
>>> Hi,
>>> 
>>> I just checked in another change... While comparing your logs I found
>>> that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
>>> 
>>> Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
>>> 
>>> Also, I noticed that aqb5 included "BANKID" which you log from aqb6
>>> didn't contain that line...
>>> 
>>> However, I think the unexpected element "LANG" (instead of "LANGUAGE")
>>> was what made the server reject the request due to syntax error...
>>> 
>>> Fixed in git.
>>> 
>> 
> 
> 
> -- 
> "Things are only impossible until they're not"

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[Chris Graves]

John,

You are probably right, but here is an excerpt from the working ofx.log
file, so I guess I'm not sure what enabled this progress:
Sending:
-
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:NONE
NEWFILEUID:20200318152018.000




20200318152011.000
xxx
xx
ENG

KINECTA
322278073


On Wed, Mar 18, 2020 at 5:10 PM John Ralls  wrote:

> Chris,
>
> You have it backwards: Martin changed LANG -> LANGUAGE because that's what
> AQB5 used.
>
> However, I just tested on a bank account at USAA and that worked, except
> that it crashed GnuCash when trying to process the new transactions. That's
> probably not AQBanking's doing and I'll look into that separately.
>
> Next I'll try Martin's command-line test.
>
> Regards,
> John Ralls
>
>
> > On Mar 18, 2020, at 4:57 PM, Chris Graves  wrote:
> >
> > John,
> >
> > In your ofx.log file it still says LANGUAGE instead of LANG.  Mine says
> LANG, which is what Martin just fixed.
> >
> > On Wed, Mar 18, 2020 at 4:54 PM John Ralls  wrote:
> > Progress indeed, though still not enough for USAA. :-(
> >
> > Regards,
> > John Ralls
> >
> >
> > > On Mar 18, 2020, at 4:48 PM, Chris Graves 
> wrote:
> > >
> > > Wow! making serious progress now.  I was requesting transactions from
> my checking account.  Looking at the ofx.log file, they were returned!!!
> > >
> > > However the import process indicated that there were no transactions
> to be imported.
> > >
> > > On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss 
> wrote:
> > > Hi,
> > >
> > > I just checked in another change... While comparing your logs I found
> > > that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
> > >
> > > Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
> > >
> > > Also, I noticed that aqb5 included "BANKID" which you log from aqb6
> > > didn't contain that line...
> > >
> > > However, I think the unexpected element "LANG" (instead of "LANGUAGE")
> > > was what made the server reject the request due to syntax error...
> > >
> > > Fixed in git.
> > >
> > >
> > > Regards
> > > Martin
> > >
> > >
> > > Am 19.03.20 um 00:26 schrieb John Ralls:
> > > > That's what mine says:
> > > > char flags="forceSsl3", "sendShortDate"
> > > > char bankName="USAA Federal Savings Bank"
> > > > char org="USAA"
> > > > char fid="24591"
> > > > char serverAddr="https%3A%2F%2Fservice2.usaa.com
> %2Fofx%2FOFXServlet"
> > > > char appId="QWIN"
> > > > char appVer="2300"
> > > > char headerVer="102"
> > > > int  httpVMajor="0"
> > > > int  httpVMinor="0"
> > > >   }
> > > >
> > > > Regards,
> > > > John Ralls
> > > >
> > > >
> > > >> On Mar 18, 2020, at 4:15 PM, Martin Preuss 
> wrote:
> > > >>
> > > >> Hmm, maybe the server is picky about the HTTP version? Some servers
> > > >> are... That can currently only be changed directly in the
> configuration
> > > >> file:
> > > >>
> > > >> $HOME/.aqbanking/settings6/users/*.conf
> > > >>
> > > >> Some servers only accept httpVMinor="0"...
> > > >>
> > > >>
> > > >> Regards
> > > >> Martin
> > > >>
> > > >>
> > > >>
> > > >> Am 18.03.20 um 23:20 schrieb John Ralls:
> > > >>> Sigh, that's not it either:
> > > >>> Sending:
> > > >>> -
> > > >>> OFXHEADER:100
> > > >>> DATA:OFXSGML
> > > >>> VERSION:102
> > > >>> SECURITY:NONE
> > > >>> ENCODING:USASCII
> > > >>> CHARSET:1252
> > > >>> COMPRESSION:NONE
> > > >>> OLDFILEUID:NONE
> > > >>> NEWFILEUID:20200318151247.000
> > > >> [...]
> > > >>
> > > >> --
> > > >> "Things are only impossible until they're not"
> > > >
> > >
> > >
> > > --
> > > "Things are only impossible until they're not"
> >
>
>
___
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.

Re: [GNC] General Ledger

[Adrian Yong]

Thanks Adrien..

On Thu, 19 Mar. 2020, 08:29 Adrien Monteleone, <
adrien.montele...@lusfiber.net> wrote:

> If they find info is missing or they don’t care for the formats, report
> back here and we’ll try to help you refine them.
>
> Regards,
> Adrien
>
> > On Mar 18, 2020 w12d78, at 6:01 PM, Adrian Yong <
> adrianyong.88p...@gmail.com> wrote:
> >
> > Thank you very much, Adrien, Michael and Stephen for helping me
> understand
> > Gnucash...
> >
> > I will submit the documents as suggested by Stephen and see what the
> > auditors say... They are CPAs...
>
> ___
> 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.
>
___
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.

Re: [GNC] AQBanking OFX DirectConnect

[John Ralls]

Chris,

I guess in your case it was having OFXHEADER:100 and VERSION:102. I think 
that's all that changed between your last failed run and the successful one.

Regards,
John Ralls

> On Mar 18, 2020, at 5:21 PM, Chris Graves  wrote:
> 
> John,
> 
> You are probably right, but here is an excerpt from the working ofx.log file, 
> so I guess I'm not sure what enabled this progress:
> Sending:
> -
> OFXHEADER:100
> DATA:OFXSGML
> VERSION:102
> SECURITY:NONE
> ENCODING:USASCII
> CHARSET:1252
> COMPRESSION:NONE
> OLDFILEUID:NONE
> NEWFILEUID:20200318152018.000
> 
> 
> 
> 
> 20200318152011.000
> xxx
> xx
> ENG
> 
> KINECTA
> 322278073
> 
> 
> On Wed, Mar 18, 2020 at 5:10 PM John Ralls  wrote:
> Chris,
> 
> You have it backwards: Martin changed LANG -> LANGUAGE because that's what 
> AQB5 used.
> 
> However, I just tested on a bank account at USAA and that worked, except that 
> it crashed GnuCash when trying to process the new transactions. That's 
> probably not AQBanking's doing and I'll look into that separately.
> 
> Next I'll try Martin's command-line test.
> 
> Regards,
> John Ralls
> 
> 
> > On Mar 18, 2020, at 4:57 PM, Chris Graves  wrote:
> > 
> > John,
> > 
> > In your ofx.log file it still says LANGUAGE instead of LANG.  Mine says 
> > LANG, which is what Martin just fixed.
> > 
> > On Wed, Mar 18, 2020 at 4:54 PM John Ralls  wrote:
> > Progress indeed, though still not enough for USAA. :-(
> > 
> > Regards,
> > John Ralls
> > 
> > 
> > > On Mar 18, 2020, at 4:48 PM, Chris Graves  wrote:
> > > 
> > > Wow! making serious progress now.  I was requesting transactions from my 
> > > checking account.  Looking at the ofx.log file, they were returned!!!
> > > 
> > > However the import process indicated that there were no transactions to 
> > > be imported.
> > > 
> > > On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss  wrote:
> > > Hi,
> > > 
> > > I just checked in another change... While comparing your logs I found
> > > that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
> > > 
> > > Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
> > > 
> > > Also, I noticed that aqb5 included "BANKID" which you log from aqb6
> > > didn't contain that line...
> > > 
> > > However, I think the unexpected element "LANG" (instead of "LANGUAGE")
> > > was what made the server reject the request due to syntax error...
> > > 
> > > Fixed in git.
> > > 
> > > 
> > > Regards
> > > Martin
> > > 
> > > 
> > > Am 19.03.20 um 00:26 schrieb John Ralls:
> > > > That's what mine says:
> > > > char flags="forceSsl3", "sendShortDate"
> > > > char bankName="USAA Federal Savings Bank"
> > > > char org="USAA"
> > > > char fid="24591"
> > > > char serverAddr="https%3A%2F%2Fservice2.usaa.com%2Fofx%2FOFXServlet"
> > > > char appId="QWIN"
> > > > char appVer="2300"
> > > > char headerVer="102"
> > > > int  httpVMajor="0"
> > > > int  httpVMinor="0"
> > > >   }
> > > > 
> > > > Regards,
> > > > John Ralls
> > > > 
> > > > 
> > > >> On Mar 18, 2020, at 4:15 PM, Martin Preuss  wrote:
> > > >>
> > > >> Hmm, maybe the server is picky about the HTTP version? Some servers
> > > >> are... That can currently only be changed directly in the configuration
> > > >> file:
> > > >>
> > > >> $HOME/.aqbanking/settings6/users/*.conf
> > > >>
> > > >> Some servers only accept httpVMinor="0"...
> > > >>
> > > >>
> > > >> Regards
> > > >> Martin
> > > >>
> > > >>
> > > >>
> > > >> Am 18.03.20 um 23:20 schrieb John Ralls:
> > > >>> Sigh, that's not it either:
> > > >>> Sending:
> > > >>> -
> > > >>> OFXHEADER:100
> > > >>> DATA:OFXSGML
> > > >>> VERSION:102
> > > >>> SECURITY:NONE
> > > >>> ENCODING:USASCII
> > > >>> CHARSET:1252
> > > >>> COMPRESSION:NONE
> > > >>> OLDFILEUID:NONE
> > > >>> NEWFILEUID:20200318151247.000
> > > >> [...]
> > > >>
> > > >> -- 
> > > >> "Things are only impossible until they're not"
> > > > 
> > > 
> > > 
> > > -- 
> > > "Things are only impossible until they're not"
> > 
> 

___
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.

Re: [GNC] AQBanking OFX DirectConnect

[chris graves]

Yeah, and perhaps I wasn't following your advice of:

It actually requires make uninstall && make clean && make && make install to 
ensure that the changed code is used.

> On Mar 18, 2020, at 5:32 PM, John Ralls  wrote:
> 
> Chris,
> 
> I guess in your case it was having OFXHEADER:100 and VERSION:102. I think 
> that's all that changed between your last failed run and the successful one.
> 
> Regards,
> John Ralls
> 
>> On Mar 18, 2020, at 5:21 PM, Chris Graves  wrote:
>> 
>> John,
>> 
>> You are probably right, but here is an excerpt from the working ofx.log 
>> file, so I guess I'm not sure what enabled this progress:
>> Sending:
>> -
>> OFXHEADER:100
>> DATA:OFXSGML
>> VERSION:102
>> SECURITY:NONE
>> ENCODING:USASCII
>> CHARSET:1252
>> COMPRESSION:NONE
>> OLDFILEUID:NONE
>> NEWFILEUID:20200318152018.000
>> 
>> 
>> 
>> 
>> 20200318152011.000
>> xxx
>> xx
>> ENG
>> 
>> KINECTA
>> 322278073
>> 
>> 
>> On Wed, Mar 18, 2020 at 5:10 PM John Ralls  wrote:
>> Chris,
>> 
>> You have it backwards: Martin changed LANG -> LANGUAGE because that's what 
>> AQB5 used.
>> 
>> However, I just tested on a bank account at USAA and that worked, except 
>> that it crashed GnuCash when trying to process the new transactions. That's 
>> probably not AQBanking's doing and I'll look into that separately.
>> 
>> Next I'll try Martin's command-line test.
>> 
>> Regards,
>> John Ralls
>> 
>> 
>>> On Mar 18, 2020, at 4:57 PM, Chris Graves  wrote:
>>> 
>>> John,
>>> 
>>> In your ofx.log file it still says LANGUAGE instead of LANG.  Mine says 
>>> LANG, which is what Martin just fixed.
>>> 
>>> On Wed, Mar 18, 2020 at 4:54 PM John Ralls  wrote:
>>> Progress indeed, though still not enough for USAA. :-(
>>> 
>>> Regards,
>>> John Ralls
>>> 
>>> 
 On Mar 18, 2020, at 4:48 PM, Chris Graves  wrote:
 
 Wow! making serious progress now.  I was requesting transactions from my 
 checking account.  Looking at the ofx.log file, they were returned!!!
 
 However the import process indicated that there were no transactions to be 
 imported.
 
 On Wed, Mar 18, 2020 at 4:32 PM Martin Preuss  wrote:
 Hi,
 
 I just checked in another change... While comparing your logs I found
 that aqb6 uses "LANG" while aqb5 used the correct name "LANGUAGE".
 
 Also, added "CLTCOOKIE" (was set by aqb5 but missing in aqb6).
 
 Also, I noticed that aqb5 included "BANKID" which you log from aqb6
 didn't contain that line...
 
 However, I think the unexpected element "LANG" (instead of "LANGUAGE")
 was what made the server reject the request due to syntax error...
 
 Fixed in git.
 
 
 Regards
 Martin
 
 
 Am 19.03.20 um 00:26 schrieb John Ralls:
> That's what mine says:
>char flags="forceSsl3", "sendShortDate"
>char bankName="USAA Federal Savings Bank"
>char org="USAA"
>char fid="24591"
>char serverAddr="https%3A%2F%2Fservice2.usaa.com%2Fofx%2FOFXServlet"
>char appId="QWIN"
>char appVer="2300"
>char headerVer="102"
>int  httpVMajor="0"
>int  httpVMinor="0"
>  }
> 
> Regards,
> John Ralls
> 
> 
>> On Mar 18, 2020, at 4:15 PM, Martin Preuss  wrote:
>> 
>> Hmm, maybe the server is picky about the HTTP version? Some servers
>> are... That can currently only be changed directly in the configuration
>> file:
>> 
>> $HOME/.aqbanking/settings6/users/*.conf
>> 
>> Some servers only accept httpVMinor="0"...
>> 
>> 
>> Regards
>> Martin
>> 
>> 
>> 
>> Am 18.03.20 um 23:20 schrieb John Ralls:
>>> Sigh, that's not it either:
>>> Sending:
>>> -
>>> OFXHEADER:100
>>> DATA:OFXSGML
>>> VERSION:102
>>> SECURITY:NONE
>>> ENCODING:USASCII
>>> CHARSET:1252
>>> COMPRESSION:NONE
>>> OLDFILEUID:NONE
>>> NEWFILEUID:20200318151247.000
>> [...]
>> 
>> -- 
>> "Things are only impossible until they're not"
> 
 
 
 -- 
 "Things are only impossible until they're not"
>>> 
>> 
> 

___
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.