[AccessD] Transactions

Arthur,

A possibly more sophisticated approach could be achieved by having the 
records displayed on a form which is totally disabled, and with the 
Allow Additions property set to No.  And then, new records can be added 
either via
a) a separate popup single view form that does not allow access to 
existing records, or...
b) via unbound controls in the form header, and submitted to the 
transactions table via an Append Query

You might also consider this, which is what I have done in one of my 
applications recently... Use a separate form or subform for the 
"adjustment" records, in which case you can display additional fields 
for a reference to the original transaction that is being adjusted, and 
a note field for an explanation for the adjustment.

Regards
Steve


Arthur Fuller wrote:
> I've developed this software and I totally agree with the accountant's
> analysis, which reduces to: recorded transactions are history and cannot be
> edited. All you are allowed to do is add an adjustment that refers to some
> previous transaction and supplies a positive or negative number as the
> adjustment.
> 
> My question is this: given a continuous form or datasheet presentation of
> the data, how do I prevent editing of the existing rows while also allowing
> new rows to be added? Is this as simple as the Allow Edits / Allow Deletes /
> Allow Inserts properties on the property sheet? I've never experimented with
> these, but suddenly I need to know. I need to prevent editing of any
> existing transaction but allow addition of new transactions. Is this as
> simple as those aforementioned flags on the properties sheet?
> 
> A.