File parse ambiguity - Date
Doug Laidlaw
laidlaws@murraytel.com.au
Sat, 3 Nov 2001 01:15:41 +1100
Thanks Bill. Since all the transactions in the QIF file were for Nov 1, I
changed one to 31/10/01. The program wouldn't give up easily though. It
considered the possibility that it was y/m/d, i.e. 2031 Oct 1, then decided
against it. I would have expected the Preferences setting to apply to all
dates.
Doug.
On Friday 02 November 2001 23:49, you wrote:
> On Thu, 2001-11-01 at 17:02, Doug Laidlaw wrote:
> > I am in Australia, using dates in the d/m/y format. I have set
> > Preferences to display dates in this format, but when importing QIF
> > files, the program opts for the m/d/y format, and inserts my transactions
> > for 1 Nov as Jan 1.
>
> You have two options. You can upgrade to 1.6.4, which will give you a
> choice of date formats when it can't determine which to use, or you can
> add a transaction to the file having a date that unequivocally
> determines the date format, such as "31/12/2000". You can delete that
> transaction after the import process.
>
> b.g.