[AccessD] Transactions

But user level security is history in the 2007 format.  So then what?

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Thursday, September 06, 2007 8:47 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Transactions

Access User Level security.

It all depends on how you want to do things.

I have several .mdb's on our network that are setup somewhat like this.


One example is our NCR database (small database to track our vendors).
There are two types of people that use this database.  People that only
need to view the data, and people that need to edit/update the data.
For this database, I went in and set it so that the default account
'Admin' and the default groups have read only access to the data.
Anyone opening that .mdb can view everything, but if they try to edit
anything (data or forms), they are simply denied.  I then created an
admin account (actually, have to do this first...), which does have full
rights to the database.  The users that need that access have the
appropriate .mdw on their machine, and a shortcut that opens the
database with the appropriate account and that specific .mdw.  

I have several 'test data' databases (getting real data from test
systems) where the default accounts can view and INSERT data, but
nothing else (no edit or delete).  Again, I have an admin account that
can do everything.

I'll post step by step instructions in another post.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Thursday, September 06, 2007 10:25 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Transactions

I'll bite, how do you do this in an MDB?

John W. Colby
Colby Consulting
www.ColbyConsulting.com
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Thursday, September 06, 2007 11:05 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Transactions

Why not do it at the table level?  Denying Update and Delete, allowing
Insert.

Drew
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.


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com