Multiple books in file backend?

[Derek Atkins]

Matthew Vanecek <mevanecek at yahoo.com> writes:

> Evidently, since you brought it up, there must also exist your concept
> of the 13th period.  So, accounting preferences.  As long as the tax man
> can be satisfied, and your partners/share holders...
> 
> Perhaps you can open a new set of books without closing the old one, and
> then at some point, click the "Close This Book" button to close it and
> make it un-editable...

Sure, but this makes it a bit more challenging -- it means you always
have to load all non-closed periods in order to get the balances
right.

> > So, I still believe that closed periods should be read-only..  However
> > I believe periods should not necessarily be tied to dates.
> > 
> 
> How do you get around tying a Period to dates?  I'm not thinking
> set-in-stone dates, of course.  Users should be able to configure custom
> Periods that cover a custom date range.
> 
> What else were you thinking they could be tied to?

Ok, what "date-range" would a "13th period" get tied to?

What I really mean is that just because a transaction is dated, say,
2002-12-20 does not mean it belongs in the period ending 2002-12-31.

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available