Re: no change capabilty for a transaction

[<ke...@dk...>]

On Sun, Nov 04, 2001 at 12:17:25AM -0500, Herb Richter wrote:
> 
> On Sat, 3 Nov 2001, Keld Jørn Simonsen wrote:
> 
> > Hi !
> >
> > I talked with Dieter about a need for not being
> > able to change a transaction, once it has been entered.
> > This is a requirement by Danish law, so it is important
> > for Danes sql-ledger users to have that capability.
> 
> 	Do you mean that once *any* transaction is entered it cannot be
> changed?  even if it just needs to be corrected?

I think there should be two options:
1. to "close" the books once in a while, that is, mark all
transactions up to a given time as unchangeable. Could be done as
a global variable per database, that is tested before any
change of a transaction.

2. To "close" every transaction every time a new one is entered.
This could also be a global variable per database.

I am not sure whether the granularity is good enough.
Should one be able to close only parts of a database?
Eg if there were department dependent bookkeeping, then
only for a certain department.

In all cases it should not require administrative privileges,
but should be available per database, and to the one that does the
bookkeeping. The privilege should probably be available to people that
are allowed to change the setup for a database, and available on the
preferences menu.

Kind regards
Keld