Comment 5 for bug 365065

On Sat, Nov 02, 2002 at 09:24:44AM -0600, John Goerzen wrote:
>
> Recently I moved from one US state to another, and as a result, my timezone
> changed to one hour earlier.
>
> After making this adjustment on my computer, every single date in every
> gnucash register was made one day earlier. For instance, November 8 became
> November 7.

This is really a problem with the data you imported as it did not
specify the timezone of the transaction (or gave erroneous data).
Older versions of ofx followed the spec and assumed GMT whenever there
was ambiguity. Under some circumstances this led to the problem you
have.

A long discussion upstream resulted in a compromise that follows
the spec as closely as possible while minimizing the chance of your
problem happening (IIRC, you'd have to import a bad file and then
move to one of the little used timezones in the Pacific).

You should contact the institution that is generating data that doesn't
follow the OFX spec and get them to fix the it.

As far as correcting the problem for your existing transactions,
upstream suggested only one fix: change the date for all affected
transactions to the correct date. Any future changes to your timezone
should not affect the date of the transaction.

I consider this bug closed. Please test the above solution and tell
me how it went. I won't close the bug until you respond (I'll give a few
weeks). In the meantime the severity of the bug will be downgraded to
normal.

--
James (Jay) Treacy
<email address hidden>