I've searched the forums and can find loads of info about 'user level security' and 'workgroups security'. There's so much, I'm lost in the forest.
What I can't find is at a more fundamental level.
Even if I secure access internally to what users can and can't do, what's to stop an employee directly deleting the complete database over the network as Access requires you to apply 'modify' share permissions to the backend so that network users can use the database.
We have a workgroup network (not domain), I share the backend out to users on other PC (typically XP Home and Professional) and internal access security is fine.
Am I missing something very fundamental or can anyone simply 'delete' the total backend should they so desire ??
I am building a database of in-car audio systems. Stored in this are simple things like vehicle information, audio brand and other general information. The main information I need to store includes details about speakers (position, quantity, material, range, size etc.) and amplifiers (power output, no. of channels etc.). Sounds simple I hope.
I have been thinking about this extensively and have come up with two solutions, each with its own pros and cons. My primary concern here is how the speaker and amplifier information is stored:
1) Tables specific to car regions (e.g. Rear Speakers, Front Speaker, Surround Speakers) have the fields 'Range', 'Material', Size, etc. Range and material can read their values from other look-up tables no probs. These would be linked to the main table via it's primary key in a 1-M relationship. -Pros: Ease of construction and general handling of data Flexibilty/expandability (in terms of speaker quantity) -Cons: When it comes to data entry the form would need to be continuous and continuous forms I have found to be a pain in terms of referring to individual records! I want some of these controls to conrol a diagram for my report (and input form) - such that they show/hide speaker pictures on a car diagram. Also, I have not yet figured out how to validate a continuous form in this situation or delete records from it either (should the user makes an error).
2) Again, tables specific to car regions but this time with a field for each speaker range (mid-range, tweeter, woofer, etc.) and it's associated data, tied to the main table via the main table ID in 1:M relationships. -Pros: Easy to manipulate form/report properties because every speaker has its own field Easier to remove erroneous data (I imagine) -Cons: More complex construction (and less efficient) - e.g. material occurs more than once for each record so to look up material form a central pool requires an intermediate table Many many more fields! Non-expandable in terms of speaker quantity
Similar principals can be applied to amplifiers so I haven't mentioned those.
My database is for Records Management of HSE Files. There are tables built for each of the seperate pieces of information (example: Categories contains a code column and a description column (101 - Air Management). The Data Entry form for the Files Table requires the entry of the Category code and the Category description in order to populate the Files Table. The Labels Report pulls from the Files Table, and if both the Category code and Category description are not populated in the Files Table (which is populated from the Data Entry Form) then the Labels Report does not produce the correct information. Plus, the Catagory code column and the Category description column both have to have the code in order to have the Labels Report produce the Category description (and not the code).
As well, in my Data Entry Form I would like to only enter in '101' and have 'Air Management' automagically populate (I've done it once - but it doesn't replicate through the Database to the Files Table! And then I have to input the data directly into the Files Table to make the Labels Report produce the labels. argh!).
I am wondering - do I even need the two columns in the Files Table (Category code and Category description) or should I just have the one (Category code) and somehow build the Labels report to replace the Category code with the Category description - and would that have something to do with the bound columns?
:confused: I've been pulling out my hair on this for a while, but as I have more and more files to enter into the database, I'm not so intersted in entering in data twice!
I've read and gone though quite a few of the scrips and examples for creating logins and security and i'm getting to the stage when i need to have good understanding of the different methods.
Some of the examples whilst create a user login do not really allow for security within the database whilst the build in security wizard would appear to offer that functionality.
I am thinking that I will use the Workgroup file and that method. My question is am i able to utilise the fact that if a person 'AdamA' logs onto the database which is built into the workgroup security file. am I then able to take 'AdamA' to populate a table which records actions by a user? (I can't seem to find any thread or book reference to doing this)
Is it possible to do this through vba. If security is setup for all the tables and a user goes in and creates a new table, can that table have security applied to it using code?
So maybe the creator of the table has read/write privileges but everyone else only has read only.
:confused: I can't access my database. I used many tools to scan my database password, and I had many results but I can't used any one. This's my database. Can you help me?
I am experimenting in creating security of a database, and elements within.
I started by creating a user account with a password. I then made a few mistakes, so wanted to delete the mdb, and start again.
However, when I now try to create a new database, or even open a pre existing database, I am asked for the user and password created in the now-deleted mdb.
Apart from the fact that it shouldn't ask for the user name and pasword created in the first database, I am sure it doesn't accept the password I intered in creating the account.
The easy solution would be to delete the file where Access stores user accounts. Where is it, and is it protected, such that I can't delete it? And even if the user name and password still exists somewhere, it should only apply to the database in which it was created, shouldn't it?
Just looking for a little advice on data protection. I have a split database which is accessed from the front end (forms only). All data is stored on the back end, which is hidden away from the user.
The database is password protected, and both sides use a login authentication to avoid unwanted access. However, the usernames and passwords are easily retrievable by opening the database a text document.
After I created it, the shortcut is created on the screen. Everytime needs to click the shortcut to login it.
But, when I go to database file, and then click it, it does not work, it will show the following message:
You do not have the necessary permissions to use the <name> object. Have your system administrator or the person who created this object establish the appropriate permissions for you. (Error 3033) You do not have the necessary permissions for the specified object. To change your permission assignments, see your system administrator or the object's creator.
So, is it ony the shortcut to login it? if delete the shortcut uncarefully, how to do it??
Problem 1: I setup a security, stored the security file and other files in the drive D:
it works.
after I move the files to the drive C:, then it doesn't work.
Why it doesn't work?
Problem 2: After I created security, there are acc.mdb, acc.bak, and Secured files, right. how can I add this link: "C:Program FilesMicrosoft OfficeOffice10MSACCESS.EXE" "D:acc.mdb" /WRKGRP "D:Secured.mdw" in the target to the acc.mdb file.
Because when it doesn't work, and then I created a shortcut of the acc.mdb file, then add the above code. Then it works, it give out the prompt.
Does any method instead of this, better than this?
I am trying to set up a database in which the the table portion is password protected but the query section can be manipulated or updated as users see fit. Does anyone know how to do this?
I have now finished my system that will run on a windows network. I now need to get the security setup so different users can access different pages.
I have set a list of users and specified what forms/tables they can access. The problem is, how does access know who is accessing the pages? For example, i have set 2 users - Dave G & Dave S - I have given Dave G access to the admin forms as he is the admin and I have given Dave S access to the general data input forms.
How is this enforced? How does access know which person is opening the forms. Unless access asks the user to login using their user name set in access, I cannot see how it can manage what users can do what.
I have locked down my welding data base and had some problems arise mabe someone eles has had this problem. All of the tables in other data base that are linked to the welding data base now will not allow me to utilize them I get the error message that I do not have rights too that information. Even though I have full access rights to the welding data base and can make changes at will.
We have a few access databases in a network. More and more people in our organization are using the databases so I am learning to create some user-level security.
We have access 2000.
Access links to a WIF to create user-level security.
But I think there is an easy way that anyone can get pass that.
Even if I have set all the groups and users privileges and restrictions, anyone can simply switch from one WIF to another WIF, then they would have changed all their privileges and restrictions.
Am I understanding this correctly?
If so, what can I do better secure the database.
Another question: How can I prevent someone from simply copy/delete the access file from windows? I am afraid that someone, maybe a disgruntled employee or even myself making stupid mistakes, delete the whole access .mdb file, and I would loss everything.
I do backup the file, but even if I back it up every night, if something like this happens, i would have lost a whole day of work.
I followed the security wizard and everything worked fine. However, when I move the database to another computer or another folder, it prints this message:
'You don't have the necessary permission to use (path)...'
Access security is really very confusing, thought I had conquered it but I was wrong. I have been playing with a test DB. How on earth do you reset a password for a user? I just can't see where you go to assign a new password. Managed to clear the password but then got stuck. Cheers RussG
I have a question for user-level security and workgroup.
Suppose we setup user-level security and have a workgroup with storing all username, password, and groups, if adminstrator want to change one user permission, let's say that change the user permission from update to read permission only, then the user should only have read permission, right. However, previously, the user copied the workgroup file himself before adminstrator change his permission, if he apply to his copied workgroup file, and log in the database, he can still have update permission.
So, how do I prevent the user using his copied workgroup file for the database?
The security on my database so far is justthe standard everyone has a user name and a password, no one can alter the design of a form apart from me
I am just wondering if there is any way that I can prevent people viewing and altering tables, queries etc. It would be good if when the open the database the main form comes up so they can navigate from that and they are always taken back to this and they can never see the database window
Does this have anything to do with front end and back end databases?
Sorry its a bit vauge but hopefully you will know what I mean
I want to maintain my database work log i.e., who ever opens the database (not through application) and changing the table should be saved in work log. Any way to acheive this?
I want to secure a database with two types of access: 1. Those that can view all data and make changes 2. Those who can view selective data I have tried the wizards, and find them difficult to follow.
I want to secure a database with two types of access: 1. Those that can view all data and make changes 2. Those who can view selective data I have tried the wizards, and find them difficult to follow.
Since this message board doesn't have a security forum yet :) I will just post this here: Does anyone know if there is a windows or system event I can check for to find out if something has been removed from a USB or parallel port? My program reads the code from the key at startup (there are USB and parallel versions of the key), and the program quits if the key is not found or the code is expired, but what if the user puts in the key, starts the program, and then removes the key? I thought of putting the keycode checking module on a timer that runs every minute or so, but that seems like a rather painful way of doing it. I thought maybe I could just run the code if a system change is detected . . . any ideas?
I am creating a database for use on a network. I have made a workgroup file for security purposes. I have made a shortcut that links to the workgroup file and database so it opens with the security passwords. However, if you open the shortcut properties, it shows where the database file itself is saved. A user could look at these properties, find out where the database is, go to that location, and open the database bypassing the security. How can I secure either the shortcut or database file itself so people cannot find out where the database is located and open without using the workgroup file security????
I know this question has been brought up a million times on here and I have done searches but everyone always refers to using the Workgroup Administration within Access to provide user level security. I have a database which uses this type of security but basically it is a complete pain in the backside. I run half a dozen databases off my computer and I have to change my workgroup file every time I open a new DB because I need to have different security settings on each DB.
Is there a way of securing a database without using the Workgroup option?
I found this but its not really any use because all it does is list the code for it and there are no step by step instructions for noobs like me - http://www.blueclaw-db.com/microsoft_access_security.htm
Good morning all, I have a question regarding the security features that Access has to offer, I have a very simple database that is made up of about 20 tables, I would very much like to set up some security features that allow me entry to the database as full administrator and another two users as read only access. I have managed to get the security wizard to set up the required accounts that are password protected in order to enter the database, however, I have said that one of my test accounts should be read only and not have any access to certain tables within my database,, this is not the case once I have signed in,, on the account where I have set read only to all tables I can still access the tables and add entries?? I am probably missing something very obvious, thank you very much for your help regards
