Hide/Protect Tables from imports?

[cefrancke]

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

[kaisersose1995]

On Aug 28, 3:36 pm, "[e-mail]" <[e-mail]:

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

you could put a password on the database. that way any one trying to
link to it, or import from would be prompted for the database password

[DavidB]

On Aug 28, 10:36 am, "[e-mail]" <[e-mail]>
wrote:

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

1st you shouldnt let user have direct access to your tables EVER.
2nd dont even let you users see the structure of your tables. Hide
the DB window and use code to disable the ability to use the F1 bypass
key.
3rd Set passwords to mask password.
4th if the PWs are all that sensative you shoudl never store them
anywhere. Put the password entered through some sort of 'encryption'
algorhythm and store/compare the encrypted values only.

[cefrancke]

On Aug 28, 10:08 am, DavidB <[e-mail]:

On Aug 28, 10:36 am, "[e-mail]" <[e-mail]>
wrote:

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

1st you shouldnt let user have direct access to your tables EVER.
2nd dont even let you users see the structure of your tables. Hide
the DB window and use code to disable the ability to use the F1 bypass
key.
3rd Set passwords to mask password.
4th if the PWs are all that sensative you shoudl never store them
anywhere. Put the password entered through some sort of 'encryption'
algorhythm and store/compare the encrypted values only.

1st - The question never implies direct access, EVER
2nd - The question never addressed the DB window.
3rd - What???
4th - The question is NOT about passwords.
5th - Reading IS fundamental, so read the question and think about
what it is asking.

So what you are saying is...

You can't prevent tables from being imported?

[cefrancke]

On Aug 28, 9:58 am, kaisersose1995 <[e-mail]:

On Aug 28, 3:36 pm, "[e-mail]" <[e-mail]:

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

you could put a password on the database. that way any one trying to
link to it, or import from would be prompted for the database password

Thanks,

I was wondering if there was a way to protect it without a db
password.
My application starts normally without the use of a password.

I have developed some features that will "show" certain functions
depending on the user and machine name.
This of course could be stored in a table, or in code. If I do it in
code, it becomes a code version nightmare.
If, for a given project, the info is stored in a table, I could update
the data (back end on a split database) with new users as needed,
instead of recoding/compiling/deploying, etc.(Yuk!)
However, with this data in a table, someone may be able to import or
link to it and modify the user/machine permissions for the db app
features.

Thanks for reading!

[Rick Brandt]

ce*******@yahoo.com wrote:

On Aug 28, 10:08 am, DavidB <[e-mail]:

[snip]

So what you are saying is...

You can't prevent tables from being imported?

Only with User Level Security and that is still breakable if the "breaker"
knows how to use Google and is willing to spend a few dollars. This is
analogous to asking about the most secure lock for a screen door. No matter
what you do, it is still a screen door.

So...it all comes down to your requirements and expectations. If you are
just trying to make it more difficult for (mostly) honest people then there
is a lot you can do (User Level Security being the best). If you really
need robust security then you should not store your data in an MDB file.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[paii, Ron]

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.

<ce*******@yahoo.comwrote in message
news:11*********************@y42g2000hsy.googlegro ups.com...

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

[kaisersose1995]

On 28 Aug, 18:24, "[e-mail]" <[e-mail]:

On Aug 28, 9:58 am, kaisersose1995 <[e-mail]:

On Aug 28, 3:36 pm, "[e-mail]" <[e-mail]:

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

you could put a password on the database. that way any one trying to
link to it, or import from would be prompted for the database password

Thanks,

I was wondering if there was a way to protect it without a db
password.
My application starts normally without the use of a password.

I have developed some features that will "show" certain functions
depending on the user and machine name.
This of course could be stored in a table, or in code. If I do it in
code, it becomes a code version nightmare.
If, for a given project, the info is stored in a table, I could update
the data (back end on a split database) with new users as needed,
instead of recoding/compiling/deploying, etc.(Yuk!)
However, with this data in a table, someone may be able to import or
link to it and modify the user/machine permissions for the db app
features.

Thanks for reading!

You can hide a table by right clicking on it and selecting properties.
This stops anyone from viewing it as an importable option when linking
etc. The downside is that it also disappears from query views etc
within the original database too. You can re-view it (and subsequently
re-use the table) by clicking options --view --hidden objects. I
think it is possible to hide/unhide tables using code if used in
queries etc. If i think of anything else i'll let you know