Setting up entry only access to a database on a network

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

Guest

I am developing an access database to be used to enter job requests for a
business person. The business person should have access to all information,
with the ability to change, etc. But the entry people should only be able to
enter new requests and changes only certain fields on their previous
requests. For example, we don't want them to be able to change the entry
date of the request, but they may add more information or reassign the
salesperson at a later date.

I have done a lot of Sql server, Sybase and Oracle programming, but I'm not
sure how to go about the dual types of access to data in Access. Is it
possible to provide row-level security?

I appreciate any suggestions. I am working with Access 2003 and the task is
to have the file reside on the network.

Thanks!
 
Tricia N said:
I am developing an access database to be used to enter job requests for a
business person. The business person should have access to all
information,
with the ability to change, etc. But the entry people should only be able
to
enter new requests and changes only certain fields on their previous
requests. For example, we don't want them to be able to change the entry
date of the request, but they may add more information or reassign the
salesperson at a later date.

I have done a lot of Sql server, Sybase and Oracle programming, but I'm
not
sure how to go about the dual types of access to data in Access. Is it
possible to provide row-level security?

I appreciate any suggestions. I am working with Access 2003 and the task
is
to have the file reside on the network.

Thanks!
Click to expand...

Well you've come to the right place and what you want is do-able but the
price you pay is a steep learning curve. MS Access user-level security
(ULS) is a complex and unforgiving beast when you're new to it so you first
need to read and understand MS's FAQ on the subject. There's a link to it
on my web site along with my step-by-step example. I can't stress enough
the need to back up your files before you start, it is very easy to lock
yourself out.

Good luck!

Regards,
Keith.
www.keithwilby.com
 
Hopping-in here (cos I can not see the OPs post):

I concur with what Keith says. ULS is very capable, but full of traps
for the unwary. You need to follow a detailed list of written
instructions, adding & omitting nothing.

As for your question about row-level security: Access's default
database engine (MS Jet) does provide row, and even column, level
security. You could (for example) stop user 'X' from accessing table
'T', unless he did it through query 'Q' - and 'Q' could limit its
output to selected rows and columns - but only on Wednesdays after 6pm!
(truly)

HTH,
TC
 
Back
Top