Help With Security Options

JMcQueen

Registered User.
Local time
Today, 18:00
Joined
May 14, 2003
Messages
15
Can anyone help me with the security on a database. I've created a database on my laptop that I want to put on the companies network. The only problem is that I need to limit individuals access to certain levels of the database. I've tried to use the security wizard with some success but there is one stumbling block.

I want to create the user group and have it apply to that database and that one only. When ever I've created or opened a database afterwords, it has applied the same workgroup file. So how do I get it to only use that work group for that specific database and then revert back to the null admin status for any subsequent file.

I know I havent explained that very well but I'm still very new to Access (please take that into account with any replies :D ).

Many Thanks.
 
Hmmm...ok, I've gone through about twenty pages of related threads and to be honest most of the ones that SEEM to be related to what I need have lost me! I'm still very new to Access (this is the first time that I've ever used it) and what I really could do with is a walkthrough, a Step by step guide on how to create the securirty for an individual database only. I'm sure there must be one somewhere so if anyone could help out it would be most appreciated....
 
I believe this sample might help you that I found on my travels to another access forum. This example is in Access 2000, if you need it converted let me know. I'll also attach a readme file in a second to allow you to gain access to the db.

I found it to be very helpful.

Hay
 

Attachments

Readme File

This is a file that you must read first to gain entry to the database.

Hope this helps
 

Attachments

Hayley, that really is good stuff! Is there a way that I could quiclkly and easily (remembering how 'green' I'am with Access) import them to use in my database?
 
It is easy enough to import this into your own database from the File menu, Get External Data, Import however you will need to remember that your field names will be named differently.
 
Last edited:
Hayley,

Your example is one of the better attempts I have seen for creating your own security without using true Access with workgroups and permission's.

How do you prevent a user from linking to the tables in your db?

How do you prevent a user from importing your database objects into there own db's?

I noticed your AllowBypass code but I did not see where you were calling it. I am assuming that you are disabling the Shift key to prevent the users from accessing the database objects from within your db.

For the novices... you must remove the standard menu/tool bars and disable the right click option or else your users will be able to access your db objects.
 
Hayley,

I was wondering if you could help me. The security demo that you provided works fine on my laptop in either converted 2002 mode or it original state. However, When I open it up on our company network I get an error message. I'm a bit baffledby this as our company uses Access 97 so I would have thought that it would be ok. I've attached a couple of pic's to show you the problem
 

Attachments

That error message could mean you are mssing a library reference. Did you download the access2000 version or the 97 version from the post?

You can post me a cut down version of the database if you are still having problems and I'll have a look, although I am going away for a few days so wont pick it up until I return, unless someone else can help before then.

Ghudson, apologies I must have missed your post first time around. The users would be blocked from seeing the database window altogether so would not have access to the tables at all. This example does allow you to see the tables so that you can see the setup behind it.
 
The trouble I am having with this type of security is as follows:
Even if the Db window is hidden, and even if the tables are hidden,
if you create a blank (empty) Db and select "Show hidden objects" from the tools-options, then right click when in the Db window and select import, you will be asked for the Db to import from. If you select the security2000 Db ALL the tables are shown. It is simply a matter of importing the Username table and removing the PASSWORD mask and all the user names and passwords will be there :(

I just wish the Access security was a bit more user friendly. I have had several attempts without much success (read minor disaster)
Dave
 
Good point Dave, I hadn't really considered that. I have been looking into this today since reading your post and came accross an article which might just work. Now I'm not too clued up on this but I have tested it and the database appears to be working and the table I tried it with does not show in the blank database when trying to import from the security demo so might be worth a try.

Here's what I found on the web:

Q) Can I hide a table so that it doesn't appear in the Database window?

(A) If you want to hide a table in the database windows so that other users can't select it, preface the table's name with 'Usys'. For example, if your table's name is employee, change it to UsysEmployee. This makes your table into a system object which access does not display. To see this table later, choose view, options, show system objects.

Now all I did was put Usys in front of tblSecurity and changed this in the code as well. Now open a balnk db and try to import tblsecurity it's now unavailable.

Is this a solution?
 
So selecting view, options, show system objects in the new db doesn't show the systems objects in the db that you are trying to import from?
 
In the blank Db when I choose File, Get External Data Import then select the securitydemo db, under tables there is nothing shown to import - the tables are hidden so they cannot be taken accross to the new db. If the tables were available to import (like they were previously) then selecting show system objects would show the system objects in the new db.
 
Hayley, do you work at Scotland Yard ?
Great invesigative work.
I will give this a go.
:)
Dave
 
Not so fast.:(
I just renamed a table with the Usys prefix and it immediately dissapreared.
From the second database, in the options menu select show system Objects and then when trying to import, the Usystable is still able to be imported. We'll keep trying.
Dave
 
Scotland Yard? erm no but I'm a private detective:p

Anyhow hope it works for ya, pay you back for your help with the help file..one good turn deserves another

Good luck
Hay
 
you always create problems don't you? Will need to try that....here we go again:rolleyes:

just tried it..back to square one I guess
 
Last edited:

Users who are viewing this thread

Back
Top Bottom