[AccessD] Transactions

Oh sure, the bigger the system, the more bells and whistles you have.
But Access User Level security (no comments yet on the posted example I
put up) does it's job just fine. 

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Thursday, September 06, 2007 4:23 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Transactions

I definitely like that concept, Drew. Not quite as clean as
Roles+Permissions in SQL, but it will suffice for the problem at hand.

A.

On 9/6/07, Drew Wutka <DWUTKA at marlow.com> wrote:
>
> One of the many reasons I use .asp and VB front ends, no direct .mdb
> access.
>
> IMHO, though, data integrity done only through the GUI is to easy to
get
> around.  F11 or Window --> unhide will always let someone at the
> database window.  So if a user shouldn't be able to change data in a
> table, that table should be secured at the table level, not the form.
> (Not too mention, securing it at the table level once, makes EVERY
form
> created have the same limitations, since the forms are going through
the
> table. (And queries....)
>
> Drew
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
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.