"correcting" transactions

[Maf. King]

On Fri 21 February 14 10:01:04 R. Victor Klassen wrote:
> Just to throw one other perspective into the list, the current discussion
> has strayed into the realm of what can and cannot be traced/changed and why
> one can never really make a transaction truly “read only”.
> 
> Thirty years ago it was “well known” (but not necessarily widely
> acknowledged) that the reasons for protection (passwords, file permissions,
> etc. ) were, in order 1) to help keep users from shooting themselves in the
> foot; 2) to protect users from other users trying to be helpful but
> actually shooting them in the foot; and 3) to protect against malicious
> users.
> 
> Too often we think only of case 3) without considering case 1).
> 
> I would love the ability to set a date range read only - with the ability to
> over-write the read-only nature of the transaction with a warning.   That
> way if I accidentally enter a transaction with an unreasonable date (and I
> got to choose what was reasonable) I would be warned, and avoid having to
> search for a transaction because it disappeared to some date I didn’t
> intend.  

Hi Victor,

A good point about foot-shooting.   Maybe an RFE (if there isn't one already) 
to pop up a warning if the date entered isn't within the default date range 
set in the properties/prefs dialogue would be appropriate...

0.02
Maf.