Is Access security? - Detailed explanation of QA security qa
Is Access security? - Access security QA explained that many friends encountered security issues about Access when using MDB files, here they answer everyone in Q & A: Q MDB I use [start] all options False, start with the cover form, the user of the same working group is not authorized to be able to make a table modification, but he can build an empty database, modify the import or link, how to prevent? Please enlighten me! A First, you should use the MS Access Workgroup Administrator program to build your own MDW file, such as Newsystem.mdw, then create a new account such as Newadmin, default with amdin, such as guest account, then set the password of each account. Then login in a Newadmin account, establish a database, or import tables or forms in an existing database. Set the security of the database. In addition to the NewAdmin account, all groups and users are blocked by the open permissions of the database, and other permissions should also be shielded. This is safe. This way to open the database can only be associated with a newly created MDW file and use the newMin account to open. But when practical applications, you should also establish an account of the software, such as Newuser, (preferably not to use the default "user" account, you can enter the system.mdw, even if you set your password is not safe, because Copy can be associated with a new system.mdw.) Corresponding the newuser account to the permissions of each table, you can read and write, can not modify the design, can only run the form, in short it is used. Shielding everything can be modified. This kind of development and run is two accounts, but the new question is if it is handed over to the user, then the user must know the password of the newuser account, then the data is not safe, so I should use VB or Delphi. A set of packages, the simplest write, running the database, such as:
strRunShell = "c: / Program Files / Microsoft Office / Office / MSACCESS.EXE / nostartup" strRunShell = strRunShell & "/ wrkgrp c: /newSystem.mdw c: /pinewood.mde / user newUser / PWD yourpassword" RetVal = Shell ( Strrunshell, vbmaximizedfocus) Of course, this is just a meaning, writing other in this set, such as checking whether Access is installed, the path is right, is it registered, etc. (Attach: With another database that has been compiled into a MDE file can also achieve the above effect) Q User Safety Group I have used it, but the security I refer is mainly for internal staff, the master outside, is like Lin, do not talk about safety at all . Access has a fatal problem (perhaps I will not use), its security performance can only be used in the currently set security mechanism, and the user has now useful, and the user simply logs in to Access with his account. Create a new * .mdb, use the link function to link the tables of the backend database (or the front-end database, because the table of the front-end database is the table on the rear database, he is nothing more than a link) As long as he read the content of the table, he can arbitrarily modify it. In fact, Microsoft's slight change Access makes it safe to apply all databases instead of the current database. We don't have to hurt their brains to prevent some of the first brothers. As our security mechanism, it is nothing more than to prevent these internal users illegally revised, destroyed. So we need an Access system-level security mechanism or Office developer Edition also has a certain help A wrong. Both links (or the front-end database can also, because the table of the front-end database is the table on the rear end database, he is nothing more than a linked), as long as he read the content, you can arbitrarily modify it. " Wrong! If Access's security is really like Xian Shi, the possibilities I have pasted may be empty. You may still have done in practice. In fact, it will be like that, because I am a newly created system file (ie MDW file), associated with new system files to create a database, and this database open permission can only be used by fixed users, such as Newuser So others, no matter what the associated database is unable to use the new database link, if so, Access has been eliminated! If you don't believe that I can do a database to send it to you, see if you can open it. I started using Access in 1997, I have to test it repeatedly for the various databases I have finished. If you can, if you can, I have accumulated dozens of people to develop the database I want to break. . . .
Q Obiki still doesn't understand: The user refers to the internal operator in the article, I have also done a lot of tests: I have established a security mechanism database, the system creates a MDW file, I set a new read only one Working Group and a general user (no administrator rights), put the system's user group does not have any permissions, then exit Access, select the new MDW file, log in with that ordinary user, create a new file, then import, Links the database for the previous security mechanism. A You may still don't care about my post, in fact, there is a more detailed explanation in the help of Access, very detailed. But in order to completely let you understand, I will column a fool-style step, and the sage is not mind, I also read the fool-style help gradually become smart. 1. Create an MDW file with the WRKGADM.EXE program in the Access installation directory. Then associate. 2, after logging in to Access, the default is the admin user, set up MDB, modify the Admin user password, build a new account, such as Pinewood, as the future management, then build a newuser, give me the user later . (You may not establish any group) 3, re-login, log in with Pinewood, then modify the password, that is, modify the empty password. Repeat once to the NewUser account. 4. Log in with a Pinewood, establish the database MDB source file you need to develop, and you can set the security after the name is, for example, MyCode saves. Security settings You should know where, there are in the menu. Push all admin and guest to any permissions for MyCode, pay attention, any permissions, whether the new table or the new module, or the open permission to the database, completely. Then all the privileges of this database are also full of all permissions. Can not miss it. If the user group does not shield its permissions, the admin and guests belonging to this group can open the database. 5, then set PINEWOOD to the database's permissions, of course, should be all permissions. Setting the newuser authority, of course, in addition to modifying design permissions, the permissions of the read and writes should be made, and the permissions to open the database should also be there. In short, this account is for users. 6, then do development, establish a form form. You have done it, then import it. But at this time your database is safe, others cannot get anything from Mycode. Unless you know your password. 7. After the development is finished, it should be separated database, not until you do this, then let the background MDB database is the same. Then compile the front desk program as the MDE file. 8, do an exe file, I said in other posts, simply use the NewUser account to open the exe file of the database. It is for your users so that they don't have any other ways in addition to using this EXE. 9, then put the MDB to the server side, MDE and MDW, and EXE release to the user. Of course, the relationship between MDE and MDB is established and debugged in advance. How to deal with how to deal with the programming is not said. 10. It is enough to do this. It is still necessary for developers who need a safe need to do. See my other posts. "Note" said some. Those problems are used naturally, and they are not used.
