[No Thirst Software] Re: Problem reconciling overlapping statements

[Alan Schmitt]

On 4 janv. 09, at 22:17, Kevin Hoctor wrote:

On Jan 4, 2009, at 1:45 PM, Alan Schmitt wrote:

Were you able to reproduce this bug? It just happened again (a
reconciled statement became open again because some old transactions
were included in it), and it's a pain to manually tweak the starting
balance to get things to work out.

Hi Alan,

I could not reproduce this but I think your method may be flawed. You
shouldn't ever have to overlap statement date ranges. If a transaction
is not reconciled, it will show up on the reconcile screen even if the
date of that transaction is much older than the range.

So I guess my question is: what is the date range used for?

Ah, I did not know that. As these transactions were grayed out, I thought I had to change the date range, but after trying I see that I can click on the transaction.

Once you
reconcile a transaction, the reconcile date is updated.

Thanks,

Alan

I think I'm starting to understand how it works: a transaction is included in a statement if its reconciliation date belongs to the statement's date range. Is this it?

PGP.sig
Description: This is a digitally signed message part