ace filled to make it two digits for day and
> year but not for month and a forward tick was used to mark that it was year
> 2000 and afterwards)
> - before year 2000, the format is “D3/25/97” (March twenty five
> nineteen nighty seven – the month day and year were all simply bro
happens for example from D12/23/99 to D3/24' 0
when y2k hit. GNC did not mind spaces in any field and it simply ignored
them so the script above made minimal change to be able to import the
modified QIF file into GNC.
When prompted by GNC during QIF import, you can tell it that it is in M/D/Y
form
s)
- before year 2000, the format is "D3/25/97" (March twenty five
nineteen nighty seven - the month day and year were all simply broken up by
a slash).
The rollover of the format happens for example from D12/23/99 to D3/24' 0
when y2k hit. GNC did not mind spaces in any field and
The supported formats are, IIRC:
y-m-d
y-d-m
d-m-y
m-d-y
Every time you start an import it will begin with the full list and use
the dates in the file to rule out from the list; if there remains more
than one once all the file is loaded, then it asks you. If the set is
empty once the file is
If you read Derek's reply again, he stated that you must use numbers only;
month names are not acceptable.
Dan
On December 29, 2022 3:14:02 PM Peter West wrote:
What date formats ARE supported by the GNC QIF import process? 29 December
2022 is unambiguous, but apparently unsupported by GNC.
What date formats ARE supported by the GNC QIF import process? 29 December 2022
is unambiguous, but apparently unsupported by GNC.
Happy 6th day of Christmas!
—
Peter West
p...@pbw.id.au
And the angel said to them, “Fear not, for behold, I bring you good news of
great joy that will be for all
Thank you Derek,
I understood *why* it was happening, and I do realize that in reality, as the
file size grows, the chance of having all days <= 12 is pretty darn slim :-)
I appreciate the quick response.
Tim
> On Dec 29, 2022, at 12:55, Derek Atkins wrote:
>
> Not particularly.
> The
Not particularly.
The issue is that 11/12 is ambiguous. Is it November 12 or December 11?
Using a 2-digit year doesn't help.
The best way is to ensure you have a day > 12 in the mix (and a year > 31).
So using 12/29/2022 should give you a unique format.
You cannot use month names, only
I’m developing QIF files to import my old investments. I get asked every time
to confirm the date format (the entire import process is a bit long imo). The
QIF specification says I ought to be able to enter a date using `dd month
year`; for example: 29 December 2022. However, this results in an
