|
I'm in
the process of moving my users from Access 2000 to 2003 and have purchased full
licences for them all, as opposed to using the Runtime facility as we always
have in the past. This leaves me with the problem of how to stop the users
opening tables and wreaking havoc following a fatal error. It was never a
problem with Runtime, because as soon as an error occurred the whole application
closed down. I've read on this list more than once that user-level
security is best avoided, so I was wondering whether there was an easy way of
preventing table access without using it.
I
thought that creating an MDE file would be just the ticket, but that only
protects the code, and as I copy the front end to the users' machines every time
it is run, they can fiddle with that as much as they like for all I
care!
Thanks
in advance
Cathy
Please zip all files prior to uploading to Files section.
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- RE: [AccessDevelopers] Keeping users away from the... Cathy Jupp
- RE: [AccessDevelopers] Keeping users away fro... Hoffman, Tobi K \(DYS\)
- RE: [AccessDevelopers] Keeping users away... Trent Johnsey
- Re: [AccessDevelopers] Keeping users ... Toby Bierly
- Re: [AccessDevelopers] Keeping us... Trent Johnsey
- RE: [AccessDevelopers] Keeping users away fro... Cathy Jupp
- RE: [AccessDevelopers] Keeping users away fro... Hoffman, Tobi K (DYS)
- RE: [AccessDevelopers] Keeping users away fro... Hoffman, Tobi K \(DYS\)
- RE: [AccessDevelopers] Keeping users away fro... Cathy Jupp
