[AccessD] Transactions

Arthur,

    My sample db named NotesHierarchical might be of interest to you. It is available at Rogers Access Library (other developers library). Link - http://www.rogersaccesslibrary.com/OtherLibraries.asp#Tejpal,A.D.
 
    In this db, meant for recording employee's performance notes, the notes table, has a Yes/No field named Sent. Once Sent is set to true, the note in question can no longer be edited, even by the person who recorded it originally. More-over, once set to True, it can no longer be re-set to False and no back dated note can be created.

    The sample is in Access 2K file format. Reference:  DAO 3.6
 
Best wishes,
A.D.Tejpal
---------------

  ----- Original Message ----- 
  From: Arthur Fuller 
  To: Access Developers discussion and problem solving 
  Sent: Thursday, September 06, 2007 09:15
  Subject: [AccessD] Transactions


  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.