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 va
> On Oct 18, 2017, at 9:14 PM, John R. Sowden
> wrote:
>
> 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
> "Re
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.
> 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
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 knowl
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 en
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 compl
On 10/16/2017 09:52 AM, Nelson wrote:
> You're getting very defensive here David and your posts are not contributing
> to this discussion at all.
>
Hi Nelson,
This mailing list is gut wrenching to read. Sadly, it's not a new thing
for these open-source project communities to degenerate into som
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 h
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://list
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
p
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
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 t
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 repe
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.
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 tha
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 transactio
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
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 Oct
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 take
20 matches
Mail list logo
