general question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a general question and wasn't sure which area to place it. In an mdb
that I am working on I will have 2 separate groups using the same app. The
app is tracking clients. Group 1 does the implementation and enters the
initial record for each client in all areas. So each table has multiple
clients and records. Group 2 takes over following the implementation process
and would enter any subsequent records to the client(s) and also at renewal
time. My general question is how can it be prevented from someone
changing/altering the initial record that group 1 enters? There are metrixs
that are tracked. My first thought is to establish a field as to which group
is adding/entering the record and work it from there. Has anyone had to do
this? Is there some literature on how I could work thru this? Any
assistance is appreciated. Thanks in advance.
*** John
 
I have a general question and wasn't sure which area to place it. In an mdb
that I am working on I will have 2 separate groups using the same app. The
app is tracking clients. Group 1 does the implementation and enters the
initial record for each client in all areas. So each table has multiple
clients and records. Group 2 takes over following the implementation process
and would enter any subsequent records to the client(s) and also at renewal
time. My general question is how can it be prevented from someone
changing/altering the initial record that group 1 enters? There are metrixs
that are tracked. My first thought is to establish a field as to which group
is adding/entering the record and work it from there. Has anyone had to do
this? Is there some literature on how I could work thru this? Any
assistance is appreciated. Thanks in advance.
*** John

What you'll need to do, it appears, is to implement Access Security.
This is a fairly complex job, and it's easy to mess it up; get the
Security FAQ at

http://support.microsoft.com/default.aspx?scid=kb;en-us;207793

It's for A97-2000 but applies to later versions as well.

Read it CAREFULLY.

Wait until you've slept overnight.

Read it CAREFULLY - *AGAIN*.

Follow its instructions, step by step; I've secured many databases,
and I still print it out (never can find my copy) and follow it every
time. Failure to do so can leave the database inconvenient but wide
open to misuse, or even lock it up so tight nobody can even open it!

Basically, you'll have probably three user groups - Developers (you
and whoever else can make structural changes to the database), Group1
and Group2. Each group will have appropriate update privileges to the
relevant tables, or the privileges to use RWOP Queries (read the FAQ!)
to update only the fields that they should be permitted to update.

John W. Vinson[MVP]
 
Back
Top