What access right should I use ?

  • Thread starter Thread starter Greg Smith
  • Start date Start date
G

Greg Smith

We put an Access 97 database on the network. And we don't
want end user to change any database object.

If I only give him "Read Only" access right, is it OK ? I
just wonder there may be problem when he opens the DB and
has to update (write to) the LDB file.

Thanks
 
You can use workgroups,and security permissions,read
about the subject,using security you can give or deny
access to any object in your database.
 
The first thing you should do is to split the database
application to Front-End and Back-End. The Back-End
contains only Tables and re-side on a shared network
drive / dir. The Front-End contains other Access objects
and each user should have a copy of the Front-End on his /
her desktop. You can compile the Front-End to the MDE
format so that the user cannot access the code.

You can also implement Access Security if required.

Do you mean you don't want the user to modify any data?

HTH
Van T. Dinh
MVP (Access)
 
Greg Smith said:
We put an Access 97 database on the network. And we don't
want end user to change any database object.

If I only give him "Read Only" access right, is it OK ? I
just wonder there may be problem when he opens the DB and
has to update (write to) the LDB file.
Click to expand...

If the user has read-only access, he won't be able to create or delete the
LDB file and thus will lock everyone out of the database until he's logged
out. If it's only the objects (forms, reports, etc.) you want read only,
make the copy of his front-end an MDE and he won't be able to open it in
design view. If you also need to secure data, you'll need to use user-level
security. Read the security faq for specific details:

http://support.microsoft.com/support/access/content/secfaq.asp
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
1) We don't split the database to Front End and Back End
as it is pretty simple
2) We don't want end user to modify any data as they are
historial data (There is a new application for the
current data)
3) The data is located in a network drive of a Novell
Server
4) We just wonder if they read data only, is it necessary
for him to write to the LDB file ?

Thanks
 
No, because the LDB is more or less for Record-locking (while editing). In
fact, if the database is open "Read-Only", the LDB is not created IIRC.
 
Back
Top