I have very painstakingly worked out a new database and I'm about to present it to the departments who will be using it. At various times words like 'password' and 'locked' have been thrown out but as of now I have not implemented any security measures. I started reading up on the topic this morning and the general consensus seems to be that unless there is a sincere need for them the security process is excruciating.
Does anyone have specific advice or opinions on access security? If I were to do anything, I think it would be to set up working groups only allowing users access to the parts of the database they are concerned with.
I would love any opinions or advice from people with experience of this on if I should recommend such measures or try to steer the department away from them.
I'd like to say thank you to those who helped me with questions I had on my database. Even though some of you didn't even realize that you helped. Searching the forum yields answers to many questions.
So now that the database is complete, I'd like opinions. I'm attaching it as a zip file. A couple of notes. I forgot to remove the database password so it's "fornax". Also, being that I work for a very large hospital I cleared out my table and removed the logos. I hid the menus and disabled the F11 key, but there is a hidden button on the far right of the footer. A double-click will restore the menus. Also try clicking on the logo--or it's place holder.
Okay, as mentioned in another thread, I was given a huge project involving MS Access. I need some opinions on what to do for this situation, and here's the situation. So far, unless suggested a better idea, I'm going to have two databases. One database will be the final version, the other will if I want to make additions, changes, etc. They will contain the same data as users will only be using one and a relationship between the two will be created. I can't remember how to do it, but I remember there was a way to prevent users from changing anything about the Access file with the exeption of what the form and the vb code allows. I plan on creating some type of login using vb. The only access to the database I want users to have is what options the forms I create give them. Please give your opinions/suggestions so I can figure out what to do.
I work for a property management compnay and they have put me in charge of coming up with a way to go some what paperless. What they are wanting is a way to enter a work order for a particular client (i.e description of work to be done for maintenance). This would then need to be printed in a report to be faxed over to the workers. This info would then need to be pulled out and placed into an invoice where, where items could be entered such as items bought ets.
My company is willing to spend thousands for software, but I think it is insane. to do so.
I was thinking that surely this could be done in access. I have an understanding of how access works (forms, reports, tables, etc.) but I have never designed one like this.
It does not have to be complex and it does not have to have a lot of formulas, I was thinking that the total could be placed in field when the invoice info is entered. Only really calculation would be adding the total of the items.
Anyway is this something that can be done relatively easily by someone with my experience, or is this to complex.
Main table about 3000 customers with 18 fields Will input payments for each customer monthly and / or quarterly total about 12,000 per year. Plan to purge payments over 18 months old frequently. 1) Put it all in one table or break into two ? 2) As far as db size wise and efficiency, would it really matter ?
We all know we're not supposed to duplicate data right? So was wondering how people deal with the deletion of Master records.
For instance let's say I have 3 tables. tblSales tblSalesSub tblProducts
tblSales - lists the sales summary - stuff like SaleId, SaleDate, SaleTotal tblSalesSub - lists the products contained within the sale. tblProducts - is the Master list of products storing the product specifics
Now to prevent duplication of data I should just store the productId in tblSalesSub then reference that to tblProducts with an innner JOIN of some kind. But what if the Master record gets deleted? The reference is broken and NULL values are returned.
How do you deal with this? Don't allow deletion of these records?But just hide them when deleted? Duplicate data by storing the product title and description within tblSalesSub? Tell the user - tough cheese you shouldn't have deleted it should you? Any other ideas?
Hi all: I currently have a database with a list of clients, and it is to be accessible to others to enter information on clients and to add new ones. However, I want to make it so that the user who wants to add a client can easily search the database for that particular client so that they won't enter a duplicate.
I have created a search function on my form, but then it occurred to me: what if there are two people with the same last name's? At first, I wanted a search operation to display a list of client names, along with their respective ID numbers and possibly a link next to each that would take the user to the corresponding record.
However, I have no idea how to do this, and I'm unsure as to whether or not this is the best way to tackle the problem. Please, someone show me the way!
Am fairly certain that I will be asked to design and implement a Machine Status Application.
Description below is very simplistic but believe you will get the idea
Basically simple stuff at Machine Operator. He clicks a command button on a display that signifies machine is okay or not. This updates machine status. Image it just toggles between Running and Stopped.
Each minute little process runs to at 1 to Run value or to Stop value. Okay so this will get a little more complex for sure.
Now I could end up collecting data on say 100 machines. Okay so I would not expect the status change to occur any more than once per hour on average so it would be a bit like having 100 very very slow users on the system. Now the crunch. What effect (if any) would these 100 very very slow users have on performance and particularly the One much quicker user who is executing preset queries one after another for say 20 seconds every minute.
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.
