RE: [AccessDevelopers] Keeping users away from the tables!

[Cathy Jupp]

Title: Message

Thanks Tobi.  I do have a startup form so they don't see the tables in the normal course of events.  The problem is only really if they encounter a fatal error and click on End - that takes them stright to the database window.  Any suggestions for handling that gratefully received. Cathy -----Original Message----- From: AccessDevelopers@yahoogroups.com [mailto:[EMAIL PROTECTED]On Behalf Of Hoffman, Tobi K (DYS) Sent: 29 September 2005 16:53 To: AccessDevelopers@yahoogroups.com Subject: RE: [AccessDevelopers] Keeping users away from the tables! How far you go will depend on 1) how trustworthy your people are, and 2) how sophisticated they are, as far as Access goes.  First of all, make sure to go to the Startup options, hide the database window and have a specific startup form.  You may want to disable the Shift-Key option before you compile the mde, then re-enable it to keep from blocking yourself out before you close.  (One way to go is to always copy your development file, make the Shift-Key change -- and others if needed -- and compile from there.)  There are other steps beyond that, some of which need to be used with great care so you maintain your own access to the front-end, but these will keep most casual users out.   Tobi -----Original Message----- From: AccessDevelopers@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Cathy Jupp Sent: Thursday, September 29, 2005 11:40 AM To: AccessDevelopers@yahoogroups.com Subject: RE: [AccessDevelopers] Keeping users away from the tables! 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 Microsoft access developer Microsoft access help Microsoft access database Microsoft access training Microsoft access training course Microsoft access programming YAHOO! GROUPS LINKS  Visit your group "AccessDevelopers" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.