Access & Security Questions

  • Thread starter Thread starter Duncan Edment
  • Start date Start date
D

Duncan Edment

Morning folks.

I have a database that is used by 8 people within the
department, to record details of daily work. The database
is stored on a network drive and everyone accesses it from
the one location. Everything has gone fine, but now some
problems are rearing their head:

1. I am aware that the database should be split into Back
& Front End, with the FE being stored locally on each
users hard-drive. However, rather than going round each
computer individually and storing the FE on the hard-
drive, is their an easier / quicker way of doing this?

2. I am noticing problems with regard to people
accidentally / intentionally modifying other peoples
entries. Is there a way to read the ID of the person who
is logged in, and only allow them to look at their own
records? Is this something that could easily be solved by
running the "User-Level Security Wizard"? If so, can
someone please provide me with plain, simple, step-by-step
instructions on how to secure the database and allow
individual user logins?

3. Is it possible to mark previously entered records
as "read-only" and unmodifiable? For example, on a Friday
when the employees have finished, have a button
labelled "Submit" which users would click, which would
then mark all entries for the current week as "read-only"?

Yes, there are a lot of questions and a lot of problems.
Perhaps if I'd thought better at the start, these problems
would exist.

I'm hoping someone here can help me.

TIA and I await your reply(ies)!

Regards

Duncan Edment
 
The basic is this, ACCESS don't support record locking.
What this mean is that user can either see all records
in a table or see nothing at all.

My background is web, vb programming. One way to do
this is to write a web front end, you can then control
things from your program. Duncan
 
The basic is this, ACCESS don't support record locking.
What this mean is that user can either see all records
in a table or see nothing at all.
Click to expand...

Actually, that's not completely correct. If the OP will store the
Username -- obtained using User Level security and the CurrentUser()
function -- in the tables and base his data entry forms on a RWOP query,
then you can create a very effective row locking schema.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
 
Back
Top