By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,203 Members | 1,383 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,203 IT Pros & Developers. It's quick & easy.

Can I secure a single table with a password?

100+
P: 153
I've got an access table that I need to be secured. It will be on a fileshare that only people that can see the information will be able to access, I simply want to put a password on editing capabilities. Can this be done for a single table without having it be user specific but rather password specific?
Dec 20 '06 #1
Share this Question
Share on Google+
13 Replies


ADezii
Expert 5K+
P: 8,638
I've got an access table that I need to be secured. It will be on a fileshare that only people that can see the information will be able to access, I simply want to put a password on editing capabilities. Can this be done for a single table without having it be user specific but rather password specific?
I do not believe that you can supply a Password that will allow editing of a specific Table in an Access Database. How about creating a Group and allow only this Group exclusive access to this Table and no others. You would then add the appropriate Users to this Group.
Dec 21 '06 #2

nico5038
Expert 2.5K+
P: 3,072
Sorry, but Access tables are always "unprotected" when a use can see the table (s)he can manipulate it..
When your users have only the Access runtime installed and no copy from Access themselves, you'll be able to control the table as such users can only work with the form's you build and can't get the tables opened directly.
When they have a fully installed copy, then your only chance is to install MS SQL or another database supporting stored procedures and triggers.

Nic;o)
Dec 21 '06 #3

100+
P: 153
okay but since most of my code is done through the use of modules, I could make reference to another database that is password protected I guess. Or I'll just put the information in another access database and have it pulled into a temporary table in the new one, I guess.
Dec 21 '06 #4

nico5038
Expert 2.5K+
P: 3,072
Indeed, both will be valid options and by making a connection to a secured database without a password in the connection string will give a password popup.

Best however to use a non-access database as the backend.

Perhaps this MS PAQ gives some additional information:
http://support.microsoft.com/support...-US&SD=gn&FR=0

And a good book on the subject is found at:
http://www.vb123.com/map/

Success !

Nic;o)
Dec 21 '06 #5

100+
P: 153
Thanks for your reply. It turns out that I might not even have to add users. People that have access to this will only be able to get to it through a part of our network which only gives them read capability. Only myself and my direct boss have read-write on this part of the network so I went through a bunch of trouble for nothing. Anyways thanks for your help everyone.
Dec 21 '06 #6

nico5038
Expert 2.5K+
P: 3,072
Only read access can be giving trouble as Access requires the creation/update od a .ldb file that holds the users....

Nic;o)
Dec 22 '06 #7

100+
P: 153
Hmm this may potentially be a problem. I'll have to test this out. Thanks for letting me know.
Dec 22 '06 #8

100+
P: 153
I am not sure of the abilities and limits that will be imposed on the users over the network but assuming that I could run into a problem, is there a way to export all created files to something like C:/Temp on the user's computer? I am not only worried about the standard temporary file but I also temporarily fill up tables which are then exported to excel. I open a bunch of database connections then, through a bunch of VBA, selectively export important data into four separate tables. This code is then, however, cleared and the database is immediately closed and compacted after this function is run if that makes any difference in the way this code is written?
Dec 22 '06 #9

100+
P: 153
just to add to the above...^^^^ I'm not worried about people taking the information out and onto their computer...they're supposed to be able to print up reports from this anyways...I just want to make sure they can not edit any information. I also have to create a log. This is getting complicated :(
Dec 22 '06 #10

nico5038
Expert 2.5K+
P: 3,072
Simple solution could be to copy the backend .mdb e.g. overnight from the (hidden) production folder to a folder they have access to. When they would make changes this will be corrected the next day....

Nic;o)
Dec 22 '06 #11

nico5038
Expert 2.5K+
P: 3,072
Forgot to mention that when you only give your users a runtime environment (no full blown Access installation), then they can't even see the tables...

Nic;o)
Dec 22 '06 #12

100+
P: 153
okay so a new question off of my first question...when I give people read only access, will they be able to write if I open by adLockOptimistic? I mean...when I open the recordset through adLockOptimistic, I have a field in a temporary table that needs to be calculated and inserted into that temporary table before the table is exported to excel and cleared.
Dec 26 '06 #13

nico5038
Expert 2.5K+
P: 3,072
WHen the folder with the Access database is read-only they won't be able to open the database as the .ldb file can't be created/updated.
Using e.g. MS SQL or Oracle with a different Userid/Password for the (ODBC) connection would however solve this problem.

Nic;o)
Dec 26 '06 #14

Post your reply

Sign in to post your reply or Sign up for a free account.