can a access database table be read-only?

princess_kay

Registered User.
Local time
Today, 08:23
Joined
Oct 16, 2010
Messages
27
hey, does anyone know if its possible to make my access database a read only file if its viewed on somebody elses computer??? because i developed a login application which has a database, i did all the users and group permissions and accounts stuff, and even set a password for all my databases. but when i sent the program to a mates laptop, he was able to open and edit the table values in my database on his computer, how can that happen? what can i do to make it be read-only?
 
there isn't much you can if you don't make an executable-type file before you distribute it. That is: an ACCDE or MDE. I don't know everything about this, but there are a number of things you can do to minimize the risk of this happening if you don't create an executable first:

Hide the table objects in the db window. If the other person is not too smart, they won't think about right clicking on the window to unhide the hidden objects.

or: hide the db window in the Access options. If you do this though, it is only secure if you disable the SHIFT bypass option AND turn off special key usage, which can also be found in the options menu. I believe that the F11 shortcut key to bring up the db window disables when turning off the special keys, but don't quote me! The other thing that may be useful here too, is shutting off the "shortcut menus" in the options menu.

The final option of course, is to have a split database where you distribute a BE and FE file to the user. Tables in the BE only can guarantee keeping people out of them, even if you don't make an executable, because you can shut off anything you want to and not affect user experience. That just might be your best option. The other obvious alternative to that would be to keep your data on a BE server like SQL or MYSQL. If you do that, tampering with it would pretty much be impossible for the Access users.
 
Split DB into FE and BE
BE = Tables
FE = Forms, Queries, Reports, Macros and Modules

Password protect BE
Link tables in FE
It will as for password when linking
Users cannot open BE directly or link tables to another FE without password

Create forms and reports to display data
In forms you can set whether a user can change anything or not
Set Shift Bypass

Make the FE a mde, accde or accdr

Thats it
 
One trick to stop the F11 key opening the Navigation Window is to capture the keypress with OnKeyDown Event and cancel it.

To use a password to properly protect the BE from an mde or accde you need to encrypt the password string inside the application. Otherwise strings are stored as plain text in the executable and can be viewed with a hex editor.
 
Access Security .mdw

When you set up security in Access, the security settings (User IDs, User Groups, Passwords and Permissions) are saved by default in a file called System.mdw

System.mdw normally resides in the Windows/System folder on your computer. System.mdw also contains your Microsoft Office settings.

The System.mdw on my computer is different than the System.mdw on your computer. Why? I have different MS Office settings and set up than you do.

As a result, if your database is copied onto my computer and my System.mdw has no Access security settings, it lets me right in with no challenge.

The way to go is to create a new .mdw file (different name than “System”) which is in the same folder as your secured database. This file will contain your security settings for that specific database. You have to place this new .mdw in the path on your shortcut to the database so that anyone who opens the database will have to enter their UserID and Password.
 
Access Security .mdw

When you set up security in Access, the security settings (User IDs, User Groups, Passwords and Permissions) are saved by default in a file called System.mdw

System.mdw normally resides in the Windows/System folder on your computer. System.mdw also contains your Microsoft Office settings.

The System.mdw on my computer is different than the System.mdw on your computer. Why? I have different MS Office settings and set up than you do.

As a result, if your database is copied onto my computer and my System.mdw has no Access security settings, it lets me right in with no challenge.

...

That is not true. Your default system.mdw file is exactly the same as mine. Otherwise you couldn't open my mdb files.

For the rest i agree. You have to make your own work group file.

Keep a record of the pid of the created workgroup file. You need it when you need to recreate the workgroup file.

HTH:D
 
The way to go is to create a new .mdw file (different name than “System”) which is in the same folder as your secured database. This file will contain your security settings for that specific database. You have to place this new .mdw in the path on your shortcut to the database so that anyone who opens the database will have to enter their UserID and Password.[/quote]

hi, how do i do the above? i have already changed the name of the mdw and changed permissions etc, i even have a password for any databases created on my computer now, but yet my mate can still edit it, it doesnt ask him for the password like it does on my computer.
 
Split DB into FE and BE
BE = Tables
FE = Forms, Queries, Reports, Macros and Modules

Password protect BE
Link tables in FE
It will as for password when linking
Users cannot open BE directly or link tables to another FE without password

Create forms and reports to display data
In forms you can set whether a user can change anything or not
Set Shift Bypass

Make the FE a mde, accde or accdr

hi, how do you split a DB into FE and BE? i have one form and one table. how do i the following?

Password protect BE
Link tables in FE
It will as for password when linking
Users cannot open BE directly or link tables to another FE without password

Create forms and reports to display data
In forms you can set whether a user can change anything or not
Set Shift Bypass
 
Split DB into FE and BE
BE = Tables
FE = Forms, Queries, Reports, Macros and Modules

Password protect BE
Link tables in FE
It will as for password when linking
Users cannot open BE directly or link tables to another FE without password

Create forms and reports to display data
In forms you can set whether a user can change anything or not
Set Shift Bypass

Make the FE a mde, accde or accdr

Thats it

Hi, i have tried the above approach, but when my program tries to insert data into the database (user login program) i get an exception sayin something about no read permission.... is it possbible to split the database and still be able to update my database table via my program. i have one table which has 3 columns, username, password and template, i also created a form and had that has the FE but as i say i could no longer insert data in the table, any reason why?
 

Users who are viewing this thread

Back
Top Bottom