[AccessD] Transactions

A.D., I took a look at your sample.  It's nice, but the 'rules' you
mentioned are only enforced at the interface level.  Hitting F11 let's
you go make any change to the table that you want.  You could prevent
that with User Level security on the tables.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of A.D.TEJPAL
Sent: Thursday, September 06, 2007 12:03 AM
To: Access Developers discussion and problem solving
Cc: adtejpal at gmail.com
Subject: Re: [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
---------------
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI BusinessSensitve material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.