Limited access tables

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a database that's inaccessible to most of my company - and for security purposes, I'd like to keep it where it is with permissions limited

However, I have several users who need to add information to a table (by form, maybe?) and I don't want to give them free reign to get into the table itself

I'm not familiar with Access Security, so I made a db in a common/public area that everyone can get to. I just don't want folks to get to anything but what they need to enter the data, and then I can put it into the table using controls

Can someone help

Thanks
Derek
 
Any good ms-access application should hide the tables and the general
ms-access stuff anyway.

Further, there is simply no need to use security to accomplish this. All you
need is to use the start-up options.

Try downloading the following access application of mine at this web page:
(it is the 3rd one ). It is in a97, but you can convert it to a2000 or
later.

http://www.attcanada.net/~kallal.msn/msaccess/DownLoad.htm
Note how all of the ms-access interface is completely hidden. I suggest you
do the same. There is no security, or even any special code used in this
application. All I did was create a start-up form, and a custom menu. By
using the tools-start-up options, virtually all of settings are available to
completely hide, and prevent the users from messing around with the
database.
 
It's my understanding that it's either difficult or impossible to disable the SHIFT-start option (giving them access to the tables and the Database window). I'm not sure our folks would know to do that, but it would be located in a central public file area

I'll check out your area, Albert. Thank you

----- Albert D. Kallal wrote: ----

Any good ms-access application should hide the tables and the genera
ms-access stuff anyway

Further, there is simply no need to use security to accomplish this. All yo
need is to use the start-up options

Try downloading the following access application of mine at this web page
(it is the 3rd one ). It is in a97, but you can convert it to a2000 o
later

http://www.attcanada.net/~kallal.msn/msaccess/DownLoad.ht
Note how all of the ms-access interface is completely hidden. I suggest yo
do the same. There is no security, or even any special code used in thi
application. All I did was create a start-up form, and a custom menu. B
using the tools-start-up options, virtually all of settings are available t
completely hide, and prevent the users from messing around with th
database

-
Albert D. Kallal (MVP
Edmonton, Alberta Canad
(e-mail address removed)
http://www.attcanada.net/~kallal.ms
 
Derek Wittman said:
I have a database that's inaccessible to most of my company - and for security purposes, I'd like to keep it where it is with permissions limited.

However, I have several users who need to add information to a table (by form, maybe?) and I don't want to give them free reign to get into the table itself.

I'm not familiar with Access Security, so I made a db in a common/public area that everyone can get to. I just don't want folks to get to anything but what they need to enter the data, and then I can put it into the table using controls.

Can someone help?

Thanks!
Derek
Click to expand...

Why don't you try splitting your database in to a front end and back
end. Form goes on the front end. That's all the user sees. Tables and
queries and code go in the back end, in a secure folder.

You can take your existing DB and split it using Access Database
splitter tool.
Tools/Database Utilities/Database Splitter.

Try it on a copy first, to maake sure it does what you expect.

Good luck

Rosco
 
Thanks, Rosco. I actually tried that. I really have only 1 table that could get adversely altered. I have it in my department's area on the network (Access Denied for anyone not in the department) and one of the guys in IS was the guinea pig to test it. The queries I'm not worried about - I have duplicates secured. The form I have is used to append to the linked table and send an email with the appended information to me for review and acknowledgment. Unfortunately, even the IS db guru couldn't run the append query (via macro in the form) because it told him he didn't have access to the data in the table

I'd love to tie the whole kit and kaboodle into NT security authentication, but that's probably waaaaay beyond me. I'm happy I can just get a form up and running with a few short macros

Why don't you try splitting your database in to a front end and bac
end. Form goes on the front end. That's all the user sees. Tables an
queries and code go in the back end, in a secure folder

You can take your existing DB and split it using Access Databas
splitter tool
Tools/Database Utilities/Database Splitter

Try it on a copy first, to maake sure it does what you expect

Good luc

Rosc
 
Back
Top