Re: Hide/Protect Tables from imports?
- From: "paii, Ron" <none@xxxxxx>
- Date: Tue, 28 Aug 2007 13:25:07 -0500
As Rick Bandt said, if you need strong security use a SQL database and not
MDB. If you only need to store a few tables, accessible to a few users with
a need to know; move them to a 2nd backend file and used Windows file
security to allow access. Access will not have a problem unless a user
attempts to access the linked tables. Also these tables will not have
referral integrity with the 1st backend, so your forms will have to maintain
that.
<cefrancke@xxxxxxxxx> wrote in message
news:1188311817.507190.79220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a few tables with sensitive user information (passwords, etc.)
and I would like to prevent someone from opening a blank database and
importing those tables.
Is there a way to "hide" or protect these tables from being linked or
imported?
TIA
.
- References:
- Hide/Protect Tables from imports?
- From: cefrancke@xxxxxxxxx
- Hide/Protect Tables from imports?
- Prev by Date: Re: Hide/Protect Tables from imports?
- Next by Date: Re: RE and Cascade Deletes
- Previous by thread: Re: Hide/Protect Tables from imports?
- Next by thread: Fitting Datasheet "Frame" Window to Table
- Index(es):
Relevant Pages
|