I am working in Access 2000. There is a table in the database that is maintained by two employees. All other employees should only be able to view and query the table. Is there a way to do that without having them log into Access?
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.
Is there a way for people to be locked out of a table but still access the table through forms. I tried using the user security but i couldn't access the tables through the forms. So they can't change the table. But can add and modify through forms.
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)
I'm on a project to build a database for the stores in our area. Things like managers, banks, and partners obviously should be in seperate tables. Most of the information though, seems to belong directly in a table of stores. Basically each record is a store and there will be very many attributes per record (about 30+). Some attributes only relate to certain departments and only someone from that department should see that info. If I broke up the big table into smaller tables it would be the same information but every table would have to have the store number to link it all back together. From a design standpoint this is bad because the store number is redundant.
So my question is, is it a good idea to split up the table for security purposes?
My main concern is security, I can take a hit on performance or storage.
Not sure what section this should go in but it vaguley relates to access and VBA so it's in here.
After a complete nightmare trying to do some decent graphs in ASP i decided to try using excel linked to my Access DB.
I've set up my pivot tables in Excel to link to the Db on the webserver. The user can open the workbook from the website and view the reports and graphs.
The problem is the database contains sensitive data for more than one organisation.
I have a workbook for each organisation selected dynamically when the user logs in to the webpage.
I've set a parameters in the pivot table querys so that all querys will be filtered using the users organisation code.
Trouble is you can access the data source of the pivot table through the wizard and ammend the parameter to view other organisations data.
Is there a way of preventing the user from accessing this feature i.e locking the wizard?
How I can generate just the last 4 digits of the SSN need to be shown on the reports which are generated? For example if a SSN were: 123-45-6789 I would want the field to read ***-**-6789. I also would like to have actual row in table password protected on its own is this possible?
Can someone tell me how to go about adding security to a field in a linked table so that only certain people can access and modify the information? I am using Access 2002. I also wonder if someone can tell me how to modify a field in a linked table? I have tried altering and saving the changes, but it won't save them because it's a linked table. Thank you in advance to anybody who can help me out here!
I'm building a DB where I have multiple users. I would like to have all data in 1 table but only give access to records created by the individual user. Is this possible?
Alternatively, if each user has it's own table, how can I report on the sum of all tables.:confused:
: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.