Help with Splitting and Security Issues Emine 12/17/2008 4:58:09 PM Hi Everyone! I got several issues here and I really need a Step-By-Step Instructions on the following please!! BTW the database will be placed on a network and used by several people. 1. I've split my database. Now I have a backend Db with only tables on it. Where are the other objects (i.e, forms, queries, reports)? Is the backend Db only used by the Admin? If so, why do I not have access to the other objects? Did I do something wrong. 2. How do I make my Db an executable file or do I need to make it executable? And what purpose does it serve? I don't want someone who knows about the shift key or the F11 key to open the database and play around with it. 3. How do I setup security? Where do I set it up frontend and backend. Can I setup log on passwords when setting up security? 4. How do I hide the menu bar on top so that the users do not play around with the Db and are allowed very limited features (i.e, print, view and maybe couple of others). My Db is completed and I really need help to finalize it so that it can go live for testing by other users. PLEASE PLEASE can someone help me. -- Thank you all for your support and guidance. What would we all do if it weren''t people like you out there to help us? Thank you!

Re: Help with Splitting and Security Issues "Rick Brandt" <rickbrandt2[ at ]hotmail.com> 12/17/2008 7:21:52 PM Emine wrote: [Quoted Text] > Hi Everyone! > > I got several issues here and I really need a Step-By-Step > Instructions on the following please!! BTW the database will be > placed on a network and used by several people. > > 1. I've split my database. Now I have a backend Db with only tables > on it. Where are the other objects (i.e, forms, queries, reports)? > Is the backend Db only used by the Admin? If so, why do I not have > access to the other objects? Did I do something wrong. You should have TWO files after splitting. One with just tables and another with everything else. You put the one with tables on a network share, update the links in the other one (the "front end file") to point at that location, then make as many copies of the front end file as you have users, giving each of them a copy to put on their local drive. > 2. How do I make my Db an executable file or do I need to make it > executable? And what purpose does it serve? I don't want someone > who knows about the shift key or the F11 key to open the database and > play around with it. You cannot make an executable out of Access. You can make a copy of the front end file that is an MDE which locks down all of the code-based objects (forms, reports, and modules). This prevents design changes and design viewing of those objects. It does nothing to protect tables, queries, or macros. People that know how to use Shift-On-Open or F11 will have to be locked out with User Level Security. > 3. How do I setup security? Where do I set it up frontend and > backend. > Can I setup log on passwords when setting up security? Access user level security is an advanced topic (almost everyone gets it wrong the first couple times). In addition it is not unbreakable if you have a person determined to get around it so weigh those two factors before you decide to try going that route. > 4. How do I hide the menu bar on top so that the users do not play > around with the Db and are allowed very limited features (i.e, print, > view and maybe couple of others). Tools - Startup lets you hide most of the built in menus and toolbars. Again, unliess the user knows about the shift-key thing. You can disable the shift-key, but if the user knows how to disable it they will also know how to re-enable it. Unless you disable it AND set up user level security. With ULS you can disable the shift-key feature in a way that only admin-users can re-enable it. > My Db is completed and I really need help to finalize it so that it > can go live for testing by other users. PLEASE PLEASE can someone > help me. Most of what is described above is not the sort of thing that you can just throw at your app at the last minute. In my opinion Access security falls into the category of "If you have to ask about it, then you are not ready to use it". How Access-savvy are your users? If they know very little about Access then the combination of Tools - Startup and giving them an MDE provides quite a bit of protection without nearly the hassle of setting up user level security. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com

Re: Help with Splitting and Security Issues "BruceM" <bamoob[ at ]yawhodotcalm.not> 12/18/2008 3:11:51 PM You posted the same question four minutes after this one in the general group for Access, where you received replies. Cross-post if you must (one message addressed to several groups), but it is considered poor newsgroup etiquette to multi-post (one message sent separately to different groups). "Emine" <Emine[ at ]discussions.microsoft.com> wrote in message news:6E4ED017-6F93-46CC-A16B-12A0E3140D5C[ at ]microsoft.com... [Quoted Text] > Hi Everyone! > > I got several issues here and I really need a Step-By-Step Instructions on > the following please!! BTW the database will be placed on a network and > used > by several people. > > 1. I've split my database. Now I have a backend Db with only tables on > it. > Where are the other objects (i.e, forms, queries, reports)? Is the > backend > Db only used by the Admin? If so, why do I not have access to the other > objects? Did I do something wrong. > > 2. How do I make my Db an executable file or do I need to make it > executable? And what purpose does it serve? I don't want someone who > knows > about the shift key or the F11 key to open the database and play around > with > it. > > 3. How do I setup security? Where do I set it up frontend and backend. > Can I setup log on passwords when setting up security? > > 4. How do I hide the menu bar on top so that the users do not play around > with the Db and are allowed very limited features (i.e, print, view and > maybe > couple of others). > > My Db is completed and I really need help to finalize it so that it can go > live for testing by other users. PLEASE PLEASE can someone help me. > > > > -- > Thank you all for your support and guidance. What would we all do if it > weren''t people like you out there to help us? Thank you!