Re: command line QIF import

[Derek Atkins]

John,

On Wed, October 18, 2017 12:14 pm, John R. Sowden wrote:
> I keep a copy of Gnucash on my computer, in the remote chance that some
> of the obvious anti-user issues would be resolved.  I ran it a moment
> ago.  I keep a copy of my chart of accounts on line, and the copy I use
> is to test various types of transactions.  The easiest for me is paying
> the rent.
>
> 1. The program opens in the Cash-Checking Account journal register.  I
> entered the check number.  For "Description", instead of a description,
> I put the name of the payee, in this case "Landlord", I entered the
> account name "Rent" I put the cursor into the credit column because I am
> reducing the cash account.  I hit enter to end the transaction.  The
> transaction I entered disappeared.  Let me clarify that: THE TRANSACTION
> DISAPPEARED.  I scrolled up, in case it scrolled off the screen, even
> though only one transaction was on the screen.  Where did the
> transaction go?  I don't know.  I am sure if I do a trial balance, I
> might find it.  If I made an error, a window should have popped up
> telling me of my error.

If you're in an Account Register, and in Basic Mode, then the transaction
you entered must be somewhere in the current account.  The first question
would be, what was the date you entered?  Second would be, what's the
current sort order?  Third, do you have a limit on the number of displayed
transactions?

The transaction didn't disappear (well, okay, it disappeared from *view*),
but it still exists in your books, somewhere.  Maybe you MEANT to put in a
different date.  How is GnuCash supposed to know that you meant e.g. six
months in the past vs six months in the future?  I.e., I'm not sure how
GnuCash could detect that you made an "error"; so if it scrolled to the
where the new transaction got put, then you'd have to manually scroll back
to the blank split for your *next* entry.  So the question is:  what's
more common?  Someone mistakenly entering the date, or someone entering a
date far enough in the past (or future) that the new transaction goes off
the screen?

> 2.  Actually this item is not an "assertion", it is an offered solution,
> as I have written a few accounting programs in my 36 years of using
> micro-computers.  By a "preference" switch, I am referring to an option
> in the "preferences" section allowing the user to select, via a check
> box, similar to choosing "Debit" or Credit" vs. the non-accounting
> titles, another transaction data entry option, one that is more user
> friendly to a bookkeeping/accounting person, even on who is not Intuit
> aware.

Um, you mean like Edit -> Preferences -> Register Defaults -> Default
Style?  The preference that's been in there for years?  You can choose
between the three modes, Basic, Auto-Split, and Journal modes.

Note that in either Auto-Split or Journal mode then you CAN enter a
transaction in a way that would make it disappear from the current open
register!  Specifically, if you don't enter the split to the current
account first (to anchor the transaction to the current register) then it
will disappear.

> Note:
> There is more to item one.  If you create an unbalanced transaction, the
> difference is silently placed into an account that is not in your chart
> of accounts.  This was discussed by several 'veterans' of this list,
> when I addressed it, and it was determined by the programmers that it
> was best to not create a pop-up "error message" window.  I disagree. 
> The solution, of course is a simple if/then structure that looks at a
> 'preferences' option, and, inside the if/then structure is the pop-up
> window. Those who choose to see a warning of their error, will see it,
> so they can correct it while all is fresh in their mind, while those
> who, like the ostrich with its head in the sand, wish to not be bothered
> with such trivialities, would merrily go on to the next transaction.

I happen to agree with you on this one -- the automatic balancing into the
Imbalance Account is annoying.  That change went in somewhere around
1.6/1.8 (I don't recall exactly when) as part of the "new" scrubbing
routines.  Personally, I'm with you -- I'd rather GnuCash force me to
create the balance, or at least pop up a dialog that would let me choose
to balance it myself or have GnuCash create the Imbalance split.

Patches always welcome!  :)

> John

> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[John R. Sowden]

I keep a copy of Gnucash on my computer, in the remote chance that some 
of the obvious anti-user issues would be resolved.  I ran it a moment 
ago.  I keep a copy of my chart of accounts on line, and the copy I use 
is to test various types of transactions.  The easiest for me is paying 
the rent.


1. The program opens in the Cash-Checking Account journal register.  I 
entered the check number.  For "Description", instead of a description, 
I put the name of the payee, in this case "Landlord", I entered the 
account name "Rent" I put the cursor into the credit column because I am 
reducing the cash account.  I hit enter to end the transaction.  The 
transaction I entered disappeared.  Let me clarify that: THE TRANSACTION 
DISAPPEARED.  I scrolled up, in case it scrolled off the screen, even 
though only one transaction was on the screen.  Where did the 
transaction go?  I don't know.  I am sure if I do a trial balance, I 
might find it.  If I made an error, a window should have popped up 
telling me of my error.


2.  Actually this item is not an "assertion", it is an offered solution, 
as I have written a few accounting programs in my 36 years of using 
micro-computers.  By a "preference" switch, I am referring to an option 
in the "preferences" section allowing the user to select, via a check 
box, similar to choosing "Debit" or Credit" vs. the non-accounting 
titles, another transaction data entry option, one that is more user 
friendly to a bookkeeping/accounting person, even on who is not Intuit 
aware.


3. I appreciate your interest in it.  Actually, because I bought my copy 
from an Egghead store years ago, I have had no need to find another.  As 
I wrote, years ago Intuit bought IHA from Craig Carlson and Stephen 
Pollack, and hired the two of them.  I received the notice in February 
of 1992.  I kept it as a compliment to IHA for their product being 
purchased by a worthy competitor.


Note:
There is more to item one.  If you create an unbalanced transaction, the 
difference is silently placed into an account that is not in your chart 
of accounts.  This was discussed by several 'veterans' of this list, 
when I addressed it, and it was determined by the programmers that it 
was best to not create a pop-up "error message" window.  I disagree.  
The solution, of course is a simple if/then structure that looks at a 
'preferences' option, and, inside the if/then structure is the pop-up 
window. Those who choose to see a warning of their error, will see it, 
so they can correct it while all is fresh in their mind, while those 
who, like the ostrich with its head in the sand, wish to not be bothered 
with such trivialities, would merrily go on to the next transaction.


John



On 10/17/2017 10:05 AM, David Carlson wrote:

John R. Sowden,

Could you please elaborate on your assertions that

1. "errors, often based on changing amounts (2 debits, etc.,) are 
hidden from the user."


2. "A 'preference' switch to allow users who are familiar and 
comfortable with the 'Intuit Way' to continue, vs. those with 
accounting knowledge who want a transaction to look like a 
transaction, could have it that way, is a possibility."


3. is "In House Accountant" available on the internet?

David C

On Tue, Oct 17, 2017 at 10:36 AM, John R. Sowden 
> wrote:


To: Liz, the moderator, and the list:

Actually Gnucash seems to strike a strong resemblance to Quicken. 
The data entry in the journal mode with no payee in the check or
source account entry (from cash, checking, or credit cards), and
where the amounts of the entry change in during the data entry
process, and where errors, often based on changing amounts (2
debits, etc.,) are hidden from the user.

It makes sense that users of the Intuit family of products want to
leave, due to some of their business practices; and some desire to
use an operating system that is not founded on enhancing the
profits of the publishers at the user's expense.

I watch Gnucash for fixes to these problems, but all I see are
justifications of why they exist.  A 'preference' switch to allow
users who are familiar and comfortable with the 'Intuit Way' to
continue, vs. those with accounting knowledge who want a
transaction to look like a transaction, could have it that way, is
a possibility.  The end result would be a transaction posted to
the appropriate accounts.

I use a DOS program run under Dosemu in Ubuntu, written by 2
programmers who sold their program to Intuit.  Intuit buried their
program, "In House Accountant", and use some of its code in
Quickbooks.  I declined their offer to 'switch'.

John Sowden
American Sentry Systems, Inc.



On 10/16/2017 07:06 PM, Liz wrote:

On Mon, 16 Oct 2017 06:52:17 -0700 (MST)
Nelson > wrote:

  

Re: command line QIF import

[John Ralls]

> On Oct 17, 2017, at 8:36 AM, John R. Sowden  
> wrote:
> 
> It makes sense that users of the Intuit family of products want to leave, due 
> to some of their business practices; and some desire to use an operating 
> system that is not founded on enhancing the profits of the publishers at the 
> user's expense.
> 
> I watch Gnucash for fixes to these problems, but all I see are justifications 
> of why they exist.  A 'preference' switch to allow users who are familiar and 
> comfortable with the 'Intuit Way' to continue, vs. those with accounting 
> knowledge who want a transaction to look like a transaction, could have it 
> that way, is a possibility.  The end result would be a transaction posted to 
> the appropriate accounts.


You’ll have a long wait, it’s not something that the GnuCash development team 
is interested in. The underlying conceptual designs of the two programs are too 
different. Quicken users who want a similar FOSS program should consider 
KMyMoney rather than GnuCash. Quickbooks users and Quicken users who are ready 
to graduate to real accounting are in GnuCash’s target audience.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[David Carlson]

John R. Sowden,

Could you please elaborate on your assertions that

1. "errors, often based on changing amounts (2 debits, etc.,) are hidden
from the user."

2. "A 'preference' switch to allow users who are familiar and comfortable
with the 'Intuit Way' to continue, vs. those with accounting knowledge who
want a transaction to look like a transaction, could have it that way, is a
possibility."

3. is "In House Accountant" available on the internet?

David C

On Tue, Oct 17, 2017 at 10:36 AM, John R. Sowden  wrote:

> To: Liz, the moderator, and the list:
>
> Actually Gnucash seems to strike a strong resemblance to Quicken.  The
> data entry in the journal mode with no payee in the check or source account
> entry (from cash, checking, or credit cards), and where the amounts of the
> entry change in during the data entry process, and where errors, often
> based on changing amounts (2 debits, etc.,) are hidden from the user.
>
> It makes sense that users of the Intuit family of products want to leave,
> due to some of their business practices; and some desire to use an
> operating system that is not founded on enhancing the profits of the
> publishers at the user's expense.
>
> I watch Gnucash for fixes to these problems, but all I see are
> justifications of why they exist.  A 'preference' switch to allow users who
> are familiar and comfortable with the 'Intuit Way' to continue, vs. those
> with accounting knowledge who want a transaction to look like a
> transaction, could have it that way, is a possibility.  The end result
> would be a transaction posted to the appropriate accounts.
>
> I use a DOS program run under Dosemu in Ubuntu, written by 2 programmers
> who sold their program to Intuit.  Intuit buried their program, "In House
> Accountant", and use some of its code in Quickbooks.  I declined their
> offer to 'switch'.
>
> John Sowden
> American Sentry Systems, Inc.
>
>
>
> On 10/16/2017 07:06 PM, Liz wrote:
>
>> On Mon, 16 Oct 2017 06:52:17 -0700 (MST)
>> Nelson  wrote:
>>
>> You're getting very defensive here David and your posts are not
>>> contributing to this discussion at all.
>>>
>>>
>>> Gnucash is Gnucash.
>> It isn't a Quicken-to-Gnucash project.
>>
>> Yes, we do get many queries about this, but the process once completed
>> is soon forgotten, and while there is much knowledge about this in the
>> mailing lists, Quicken-to-Gnucash is not the main focus of this project.
>>
>>
>> Nelson, you are free to try and do what you like, except start personal
>> attacks on other contributors.
>>
>> Liz, the moderator.
>> (Profanity is also something I heavily discourage)
>> ___
>> gnucash-user mailing list
>> gnucash-user@gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -
>> 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
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[John R. Sowden]

To: Liz, the moderator, and the list:

Actually Gnucash seems to strike a strong resemblance to Quicken.  The 
data entry in the journal mode with no payee in the check or source 
account entry (from cash, checking, or credit cards), and where the 
amounts of the entry change in during the data entry process, and where 
errors, often based on changing amounts (2 debits, etc.,) are hidden 
from the user.


It makes sense that users of the Intuit family of products want to 
leave, due to some of their business practices; and some desire to use 
an operating system that is not founded on enhancing the profits of the 
publishers at the user's expense.


I watch Gnucash for fixes to these problems, but all I see are 
justifications of why they exist.  A 'preference' switch to allow users 
who are familiar and comfortable with the 'Intuit Way' to continue, vs. 
those with accounting knowledge who want a transaction to look like a 
transaction, could have it that way, is a possibility.  The end result 
would be a transaction posted to the appropriate accounts.


I use a DOS program run under Dosemu in Ubuntu, written by 2 programmers 
who sold their program to Intuit.  Intuit buried their program, "In 
House Accountant", and use some of its code in Quickbooks.  I declined 
their offer to 'switch'.


John Sowden
American Sentry Systems, Inc.


On 10/16/2017 07:06 PM, Liz wrote:

On Mon, 16 Oct 2017 06:52:17 -0700 (MST)
Nelson  wrote:


You're getting very defensive here David and your posts are not
contributing to this discussion at all.



Gnucash is Gnucash.
It isn't a Quicken-to-Gnucash project.

Yes, we do get many queries about this, but the process once completed
is soon forgotten, and while there is much knowledge about this in the
mailing lists, Quicken-to-Gnucash is not the main focus of this project.


Nelson, you are free to try and do what you like, except start personal
attacks on other contributors.

Liz, the moderator.
(Profanity is also something I heavily discourage)
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[Liz]

On Mon, 16 Oct 2017 06:52:17 -0700 (MST)
Nelson  wrote:

> You're getting very defensive here David and your posts are not
> contributing to this discussion at all. 
> 
> 

Gnucash is Gnucash.
It isn't a Quicken-to-Gnucash project.

Yes, we do get many queries about this, but the process once completed
is soon forgotten, and while there is much knowledge about this in the
mailing lists, Quicken-to-Gnucash is not the main focus of this project.


Nelson, you are free to try and do what you like, except start personal
attacks on other contributors.

Liz, the moderator.
(Profanity is also something I heavily discourage)
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[Aaron Laws]

On Mon, Oct 16, 2017 at 8:55 AM, Nelson  wrote:

>
> That's why I am saying that having some flags to tuneup the import process
> and detailed logging would help a lot.
>

It sounds like you've identified some areas for improvement. This is a
volunteer project, so the more you can do to make this happen, the more
likely it will happen. Creating a detailed bug report would be the first
step. If you have some quite specific ways to improve the process, that
would be very helpful. If you're comfortable with C++, feel free to
contribute a patch (it doesn't need to be perfect; we can work with you,
too).
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[Nelson]

You're getting very defensive here David and your posts are not contributing
to this discussion at all. 





--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[David Carlson]

Nelson,

It sounds to me like you are unwilling make the effort to "shepherd" your
data through the import process.  Many of us, including David T are trying
to tell you that we have succeeded in completing massive imports from
Quicken into GnuCash, but we needed to take several steps to plan our
procedure, prepare the data, preprocess data and postprocess data to do
it.

Each case will vary because each of us took different shortcuts and entered
data from different financial institutions, etc. when using Quicken.  We
also have different ideas about what details are most important to preserve
vs what is "noise"

David C

On Mon, Oct 16, 2017 at 7:55 AM, Nelson  wrote:

> There are multiple classes of failures and most of them seems to be
> transfers
> related. There are the ones a which show up more often:
>
> - missing transactions
> - duplicate transactions
> - voided transactions (transaction exist but flagged as "void" and has zero
> amount)
> - transactions in wrong account (transfer from account.A to account.B
> recorded as debit account.A and credit account.C)
>
> I totally understand QIF format limitations. When I do a transfer from
> account.A to account.B, and I download the transactions from the bank in
> Quicken, account.B trx. will show up in one day while account.B will show
> up
> couple days later, maybe 2 to 5 days. While Quicken will match these
> properly, GnuCash will create duplicates most-likely, because in the
> exported QIF file  there are two different transactions,  one for account.A
> and one for account.B.
>
> That's why I am saying that having some flags to tuneup the import process
> and detailed logging would help a lot.
>
>
>
>
>
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[Nelson]

There are multiple classes of failures and most of them seems to be transfers
related. There are the ones a which show up more often:

- missing transactions
- duplicate transactions
- voided transactions (transaction exist but flagged as "void" and has zero
amount)
- transactions in wrong account (transfer from account.A to account.B
recorded as debit account.A and credit account.C)

I totally understand QIF format limitations. When I do a transfer from
account.A to account.B, and I download the transactions from the bank in
Quicken, account.B trx. will show up in one day while account.B will show up
couple days later, maybe 2 to 5 days. While Quicken will match these
properly, GnuCash will create duplicates most-likely, because in the
exported QIF file  there are two different transactions,  one for account.A
and one for account.B.

That's why I am saying that having some flags to tuneup the import process
and detailed logging would help a lot.





--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[David T. via gnucash-user]

What do you mean "failed"? They aren't in the gnucash file at all? Or, they 
import incorrectly? 
If the latter, take a look at some of the transactions that failed; is there 
something in common?  In my Quicken data, it was transactions that had no 
categories that caused the most problems. Fill things in, try again and see 
what happens. Rinse and repeat until your data is clean enough, and pick up the 
rest afterwards. 
If they didn't import at all, I don't know what to say. 
David

 
 
  On Sun, Oct 15, 2017 at 22:50, Nelson wrote:   
Thank you for your answer David.

I am aware that QIF is a text file and I can open it in text editor. 

I have a 235000 lines QIF file created by quicken. Most of the transactions
are being imported properly but there are thousands failing as well. I have
no way to identify those failed transactions other than going line by line
in each account. What shall I "edit in quicken first" to insure a successful
import?



--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[David Carlson]

I am not a developer, but I can point out that the QIF importer works in
several discrete steps where (roughly) it

1. identifies the 'source' account type and name and tries to associate it
to an existing account in the data file.  If there is more than one
'source' account in the QIF file it repeats for each.

2.  It presents it's results to the user for verification and (if
necessary) correction.

3.  Identifies all of the 'destination' accounts or categories and tries to
match them to existing accounts.

4.  It presents it's results to the user for verification and (if
necessary) correction.

5.  It parses each transaction and compares it to existing transactions
between the particular accounts previously identified.

6. It prepares lists of incoming transactions with suggested matches to
existing transactions where found.  These lists allow user editing to
accept or correct suggested matches.  This is where it is more efficient to
import only one account at a time so the 'duplicates' can be found here.

There are many checks during the import to test the text at each step and
prevent possible crashes and gross errors during matching and acceptance.

As an experienced user I would actually prefer that the developers stay out
of this discussion as they are very busy working 'under the hood' right now
toward getting the release 2.8 series into shape.  That release should get
rid of the deprecated software that is now threatening the continued
inclusion of GnuCash in (and compatibility with) upcoming Linux packages.

David C

On Sun, Oct 15, 2017 at 6:05 PM, Adam Jensen  wrote:

> On 10/15/2017 04:49 PM, Nelson wrote:
> > Thank you for your answer David.
> >
> > I am aware that QIF is a text file and I can open it in text editor.
> >
> > I have a 235000 lines QIF file created by quicken. Most of the
> transactions
> > are being imported properly but there are thousands failing as well. I
> have
> > no way to identify those failed transactions other than going line by
> line
> > in each account. What shall I "edit in quicken first" to insure a
> successful
> > import?
>
> Hi. I am very new to the list [1] and *very* new to GnuCash [2].
>
> Strangely, Nelson, I might get what you are asking far more than the
> other respondents seem to. I hope you can endure this problem, at least
> while it is being explored and discussed; rational, pragmatic people are
> vital to technical projects. ...Sometimes volunteer-based communities
> get a little cult-like in their public interface...
>
> So, I am a mature engineer [3] with some experience in
> instrumentation-sourced data wrangling (as part of large data
> organization and analysis systems); maybe I can try to steer the topic
> of file conversion/import towards the "hackers" on the list - and those
> otherwise interested in engaging such a conversation. To that end, could
> some of the software developers and maintainers chime into a technical
> discussion of the data structure issues involved in building a
> translation utility? It might be fruitful if not at least interesting :)
>
> Anyway, a belated Greetings and Salutations to you all :)
>
>
> [1]: Subscribed for about two days.
> [2]: I've only just started the semi-serious exploration, assessment and
> evaulation of the GnuCash software (and its representation of the
> historical bookkeeping/accounting processes and their
> traditional/societal basis) about three days ago - installation and one
> launch of the application on Ubuntu, one chapter of the Guide read and
> the introductory chapter of a financial Accounting book mused at.
> [3]: LinkedIn, Google::hanzer
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

RE: command line QIF import

[Ken Pyzik]

Nelson -- do you really need (want) 20 years of data?  I recently
transferred from Quicken to GnuCash because of the new goofy subscription
model -- and I have about 11 years of data.  Upon doing the import first
with all the data -- it was too complicated to try and get it right -- since
-- I had not categorized all the data in Quicken to begin with.  After
careful reflection and inspection of the source data in Quicken -- I was
able to determine that I really did not need all the data and cut down to 6
years of data. 

Then, once I imported, I was able to delete a couple more years and was able
to get everything in sync and balanced.  It took a few days -- but I think
you can do it.  Additionally, if you get "good" balances on most of the
accounts, search the 'imbalance" account for those transactions that are not
in balance.  At the end of the process - it does work.   Best of luck. 

-Original Message-
From: gnucash-user [mailto:gnucash-user-bounces+pyz01=cox@gnucash.org]
On Behalf Of Nelson
Sent: Sunday, October 15, 2017 1:50 PM
To: gnucash-user@gnucash.org
Subject: Re: command line QIF import

Thank you for your answer David.

I am aware that QIF is a text file and I can open it in text editor. 

I have a 235000 lines QIF file created by quicken. Most of the transactions
are being imported properly but there are thousands failing as well. I have
no way to identify those failed transactions other than going line by line
in each account. What shall I "edit in quicken first" to insure a successful
import?



--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[Nelson]

Thank you for your answer David.

I am aware that QIF is a text file and I can open it in text editor. 

I have a 235000 lines QIF file created by quicken. Most of the transactions
are being imported properly but there are thousands failing as well. I have
no way to identify those failed transactions other than going line by line
in each account. What shall I "edit in quicken first" to insure a successful
import?



--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Re: command line QIF import

[Dave Gillam]

I am temporarily away from my email.  If urgent, please contact Joe Miller at 
210-884-1334 or j...@davegillam.com.

Thank You,

David


On Oct 15, 2017, at 3:20 PM, D via gnucash-user  
wrote:

> Nelson,
> 
> I don't see how a command line interface would help.
> 
> Since QIF is a text file format, you could always just go through the source 
> file with a text editor first to get your data in a ship shape state and 
> *then* do the import. Or, use quicken to edit the transactions first.
> 
> David
> 
> On October 15, 2017, at 10:03 PM, David Carlson  
> wrote:
> 
> Not sure about more efficient ways to import via QIF, which, by the way, is
> reasonably efficient when done in small chunks,  but another caveat that
> has not been raised recently is that as the data file grows it takes longer
> to do the frequent file saves.
> 
> In Windows each save for my data file takes the file out of service for
> over a minute with a very fast computer.  In Linux it is still 15 or 20
> seconds.  I have about 10 years' data in my main file.
> 
> David C
> 
> On Sun, Oct 15, 2017 at 12:14 PM, Nelson  wrote:
> 
> Hi everyone,
> 
> I am trying to import about 20 years of Quicken transactions into GnuCash
> going trough a Quicken QIF export. As many people reported, this is a very
> painful process and requires endless manual corrections.
> 
> I was wondering if it would be possible to maybe to do the import from
> command line, and maybe to have more control of the process. Doing it from
> gui, there are no options to modify / adjust the process and all warnings /
> progress messages just disappear from the screen. Also, any entity
> remapping
> is not kept from one test to another and it seems that no useful logs are
> being created.
> 
> I am running this on windows and I've noticed 83 .exe files in GnuCash's
> bin
> directory. Is any of these binaries capable to do an QIF import, maybe with
> more options than the gui does and proper logging?
> 
> TIA.
> 
> 
> 
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[D via gnucash-user]

Nelson,

I don't see how a command line interface would help.

Since QIF is a text file format, you could always just go through the source 
file with a text editor first to get your data in a ship shape state and *then* 
do the import. Or, use quicken to edit the transactions first.

David

On October 15, 2017, at 10:03 PM, David Carlson  
wrote:

Not sure about more efficient ways to import via QIF, which, by the way, is
reasonably efficient when done in small chunks,  but another caveat that
has not been raised recently is that as the data file grows it takes longer
to do the frequent file saves.

In Windows each save for my data file takes the file out of service for
over a minute with a very fast computer.  In Linux it is still 15 or 20
seconds.  I have about 10 years' data in my main file.

David C

On Sun, Oct 15, 2017 at 12:14 PM, Nelson  wrote:

> Hi everyone,
>
> I am trying to import about 20 years of Quicken transactions into GnuCash
> going trough a Quicken QIF export. As many people reported, this is a very
> painful process and requires endless manual corrections.
>
> I was wondering if it would be possible to maybe to do the import from
> command line, and maybe to have more control of the process. Doing it from
> gui, there are no options to modify / adjust the process and all warnings /
> progress messages just disappear from the screen. Also, any entity
> remapping
> is not kept from one test to another and it seems that no useful logs are
> being created.
>
> I am running this on windows and I've noticed 83 .exe files in GnuCash's
> bin
> directory. Is any of these binaries capable to do an QIF import, maybe with
> more options than the gui does and proper logging?
>
> TIA.
>
>
>
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: command line QIF import

[David Carlson]

Not sure about more efficient ways to import via QIF, which, by the way, is
reasonably efficient when done in small chunks,  but another caveat that
has not been raised recently is that as the data file grows it takes longer
to do the frequent file saves.

In Windows each save for my data file takes the file out of service for
over a minute with a very fast computer.  In Linux it is still 15 or 20
seconds.  I have about 10 years' data in my main file.

David C

On Sun, Oct 15, 2017 at 12:14 PM, Nelson  wrote:

> Hi everyone,
>
> I am trying to import about 20 years of Quicken transactions into GnuCash
> going trough a Quicken QIF export. As many people reported, this is a very
> painful process and requires endless manual corrections.
>
> I was wondering if it would be possible to maybe to do the import from
> command line, and maybe to have more control of the process. Doing it from
> gui, there are no options to modify / adjust the process and all warnings /
> progress messages just disappear from the screen. Also, any entity
> remapping
> is not kept from one test to another and it seems that no useful logs are
> being created.
>
> I am running this on windows and I've noticed 83 .exe files in GnuCash's
> bin
> directory. Is any of these binaries capable to do an QIF import, maybe with
> more options than the gui does and proper logging?
>
> TIA.
>
>
>
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.