Q: linked table as append only (and security question)?

[MarkD]

Using access 2000

How does one create a table link (to a table in another
access database) that is read/append only?

Here's what I'm trying to do. We need to enforce data
security so that the end user cannot delete/update
records -- only add. My initial thought was to create an
data.mdb with the actual data, and entryscreen.mdb with
the data entry screens and links. data.mdb would be
password protected. entryscreen.mdb would have restricted
access to the tables.

Would that work? If not, what is the best way to handle
what I'm trying to do?

Thanks!
-Mark

 

[Tim Ferguson]

We need to enforce data
security so that the end user cannot delete/update
records -- only add.

What about correcting entry errors? At what point is a field committed so
that it becomes untouchable -- after the lost focus; after the record is
saved; after the form is closed; at the end of the user session?

You might want to consider a different approach, with a temp table for new
records, that are appended to the main db when the user logs off.

Another approach would be to add a field called "Locked", which is set to
True when a set of records is validated. The users could then access the
table via two RWOP queries: one read-write "WHERE Locked = FALSE", and the
other read-only without the criterion.

On the other hand, while you are still figuring out the business case^W
rules, you could implement it all in the GUI itself, by locking all the
controls in the Current event, unless the form is in Data Entry mode.

Just a few thoughts


Tim F

 

[TC]

Your proposal sounds fine, if you can accept the risk of the users opening
the back-end database directly, & making changes there.

To avoid that risk, & make it as safe as Access can make it, you'd need to
implement Access user-level security, & use Run With Owner Permission (RWOP)
queries for all access to the back-end table, from the front-end database.
But that would be a lot of work.

And as Tim said, whatever method you use, you need to have a strategy for
correcting data entry errors.

HTH,
TC


But that might be overkill. If you want it to be "reasonably" safe,