|
Home > Archive > MS Access Multiuser > August 2005 > Preventing the Import of Tables
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Preventing the Import of Tables
|
|
| Ian Davies 2005-08-10, 11:26 am |
| Is there a sure way of securing the data in an access table.
I have been doing a bit of experimenting and cannot find a way to stop
someone creating a new database and aquiring data (that they possibly
shouldnt have access to) simply by importing tables into it from the
restricted database, regardless of how that restricted database has been
secured.
Is there a known way, please?
Ian
| |
| Rainbow01 2005-08-10, 11:26 am |
| set password
when import table from protected mdb, password is also required
"Ian Davies" 來函：
> Is there a sure way of securing the data in an access table.
> I have been doing a bit of experimenting and cannot find a way to stop
> someone creating a new database and aquiring data (that they possibly
> shouldnt have access to) simply by importing tables into it from the
> restricted database, regardless of how that restricted database has been
> secured.
>
> Is there a known way, please?
>
> Ian
>
>
>
| |
| Jeff Conrad 2005-08-10, 11:26 am |
| You would need to implement full blown Access User Level
Security (ULS) and then deny all permissions to the tables
themselves. To access the data you would need to set up
RWOP queries with the needed permissions. Further steps
would then be needed to lock it down a bit tighter such as
creating an MDE file, creating custom menu bars/toolbars,
and setting restriction options under Tools | Startup.
ULS is a difficult concept to grasp the first few times so
if you have not used it, I strongly suggest reading up on the subject
by reviewing the information I have accumulated here:
http://home.bendbroadband.com/conra...s.html#Security
(Watch out for any possible line wrapping on that link)
Practice on dummy databases until you really have a feel for it.
If you really have people going where they shouldn't be
you might be better off not to use JET as the back-end.
Good luck,
--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conra...cessjunkie.html
http://www.access.qbuilt.com/html/articles.html
"Ian Davies" wrote in message:
news:TOoKe.2050$CM.199@newsfe7-win.ntli.net...
> Is there a sure way of securing the data in an access table.
> I have been doing a bit of experimenting and cannot find a way to stop
> someone creating a new database and aquiring data (that they possibly
> shouldnt have access to) simply by importing tables into it from the
> restricted database, regardless of how that restricted database has been
> secured.
|
|
|
|
|