QIF import - Inconsistent Date - How to fix?

[David T.]

Johannes' suggestion (to split the file) is a good one. 

One common problem is a date which is formatted differently than the rest (i.e. one date that uses MM-DD-YYYY format), causing the importer to freak out. This is more common with larger QIF files. All it takes is one odd date to throw the error, which is why splitting the file can help. Once you locate the problem, I would probably fix it in the full QIF file and import the entire lot at one pass.

David

On Mar 3, 2013, at 11:00 AM, Johannes Kapune <listen at kapune.de> wrote:

> Hi B.,
> 
> I have never done importing QIF-files, but when I remember reading this
> list right there are some problems with generating QIF-files out of
> different programs so gnucash does not accept.
> 
> Also I remember there was an earliest date that gnucash accepts.
> 
> Do you can break your QIF-file in parts and than try to import part by
> part (maybe first into a gnucash test file) to get out at what point it
> stops (and than correct the QIF)?
> 
> hope this helps
> 
> Johannes
> 
> 
> Am 03.03.2013 19:37, schrieb bunk3m:
>>   Thank you, David.
>>   I changed the Locale on my Mac to US and changed the date/time in
>>   Gnucash to Locale.
>>   I was able to get much further in the import process; read in QIF file,
>>   set-up & check accounts, categorize stocks, bonds, funds etc.
>>   But then it crapped out with error "A bug was detected while converting
>>   the QIF data."  OK.  And now what?  Now that description is as good as
>>   most Windows bugs!  If only it had a bug number or more info in the
>>   description, and I might have an idea of where to start.
>>   What bug might Gnucash be alluding to?
>>   Thanks again for your help.
>> 
>>   On 3/2/13 4:05 PM, David T. wrote:
>> 
>>   Try looking at this older thread:
>>   [1]http://lists.gnucash.org/pipermail/gnucash-user/2012-July/045330.htm
>>   l
>>   You might consider temporarily setting your date/locale preferences to
>>   UK for the import and seeing if that remedies the problem on import.
>>   David
>>     __________________________________________________________________
>> 
>>   From: bunk3m [2]<bunk3m at gmail.com>
>>   To:
>>   Cc: [3]gnucash-user at gnucash.org
>>   Sent: Saturday, March 2, 2013 12:57 PM
>>   Subject: Re: QIF import - Inconsistent Date - How to fix?
>>   My apologies.  The actual error message is:
>>   "Transaction date: Unrecognized or inconsistent format."
>>   On 2.03.2013 15:28 , bunk3m wrote:
>>> I'm trying to move a huge QIF file (1.6MB) with nearly 20 years of
>>   data
>>> in it over to gnucash.  I'm starting with a new empty gnucash file.
>>> 
>>> The date format export from the old program uses the system date
>>   which
>>> is dd.mm.yyyy.  (I am in Canada but prefer the dd.mm.yyyy format.)
>>   My
>>> system date is therefore custom but shows dd.mm.yyyy.
>>> 
>>> Gnucash is supposed to use the system date too????  I have set the
>>> Europe as the Date Format so it also shows dd.mm.yyyy.
>>> 
>>> How do I figure out which transactions create this "inconsistent
>>   date"
>>> error?
>>> 
>>> How do I fix the QIF so I can import all these transactions?
>>> 
>>> Gnucash 2.4.11  r22264M
>>> Mac OS Intel 10.8.2
>>> 
>>> My searches haven't found a solution :-(
>>> Please cc me directly as I'm on daily digest mode.
>>> 
>>> Thanks in advance.
>>> B.
>>> 
>> 
>> References
>> 
>>   1. http://lists.gnucash.org/pipermail/gnucash-user/2012-July/045330.html
>>   2. mailto:bunk3m at gmail.com
>>   3. mailto:gnucash-user at gnucash.org
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user at 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 at 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.