[Kmymoney-devel] Kmymoney - QIF Import Strangeness

Jack ostroffjh at users.sourceforge.net
Mon Mar 1 16:35:55 CET 2010

On 2010.02.28 20:16, aga wrote:
> In the process of making some changes in my CSV Importer, I produced  
> a QIF file (which is an optional byproduct).  To cut a long story  
> short, I produced the qif QString date, from a QDate, without field  
> separators.  On importing the QIF file, I wasn't asked about the date  
> format and KMM imported the file.
> However, the dates were incorrectly decoded, possibly because, as it  
> happened, all dates in the file were ambiguous.
> For instance, 30112009 appeared as 20.09.3011, and 29012010 appeared  
> as 20.10.2901.  The fact that the dates were accepted suggests that  
> KMM does not insist on field separators, but then in this case,  
> misinterprets the dates. There were nine dates in the file, all  
> within the above range.
> This is on 3.95.

I'm not sure what your question is.  Without knowing how KMM actually  
read (or tries to read) dates, it looks like its default is YYYYMMDD as  
long as it produces valid results.  Personally, I generally prefer this  
format anyway, since you can sort on it easily (text or alpha, with or  
without field separators).  Do you have any reason not to use this  
format in the QIFs you produce?


More information about the KMyMoney-devel mailing list