Link to Userlevel secure database

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

Guest

hi,

I have a non-secure database and want to link to a database which has user
level security. How do I go about this? do i need to also create userlevel
security on my own database? If i can get round having to secure my own
database it would be prefereable.
Ive searched the help file and can find how to link to password protected
databases but not user-level protected ones.

Thanks for your help!

Barbara
 
Hi.
I have a non-secure database and want to link to a database which has user
level security.
If i can get round having to secure my own
database it would be prefereable.

Please see the "How to open databases and only be prompted for User ID and
password for the secure databases" tip on this Web page:

http://www.Access.QBuilt.com/html/security.html

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Hi,

Thanks for your help, but this doesnt answer my questions.
I have a non secure database and I want to create a LINKED TABLE.
however the table I want to link is in a user-secure database.
Is it possible to do this without making my own database secure?
 
Hi.
Thanks for your help, but this doesnt answer my questions.

Consider it a "down payment." ;-) I had 16 windows open and I hit "Send"
on your message before it was finished. It answers one of your questions
for what you'll need to do for one of the steps that I'm about to outline,
so it's not totally irrelevant as you may think.

Your secure User ID will need "Read Design" permissions on the secure table,
along with "Open/Run Database" permissions. Preferably, this is a member of
the Admins group. You have a couple of choices on how to connect to this
table, though. You can link directly to the table, or connect to the secure
database from an unsecure database through VBA code.

In order to link to a secure database, one needs to already be joined to the
secure workgroup. You can join the secure workgroup (via the shortcut
that's mentioned in the tip that I gave you the link to), then link to the
table in the secure database. The rest of the unsecure database can remain
unsecure, but consider whether you want "just anybody" to see what's in that
table. If you don't, then secure the separate database. If it's data that
would otherwise be unsecure if it resided in a different database, then
consider keeping your separate database unsecured. (I'd recommend securing
it anyway, because later on when more tables need to be linked to, you'll
realize it would have been easier if you'd just gone ahead and secured the
database at the beginning.)

If you chose to secure the database, then create queries based upon this
linked table and assign "run with owner permissions" to the query so that
users can use the data without having any permissions on the table (these
would just be members of the Users group, not the Admins group). These
queries would be used as recordsources for forms, reports and procedures in
modules or classes.

Another way to "link" to the secure table is to programmatically open the
secure database from the unsecure database using the User ID and password
provided by the user from a form at run time, then create a recordset from
the secure table to be used as a recordsource for the forms, queries,
reports and procedures in modules or classes in the separate database. This
requires some expertise in VBA coding, so you may not want to go this route.
The same considerations apply regarding whether you want to keep the
separate database unsecure or secure it: whose eyes do you _not_ want to
see the data in that table?

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Hiya,

thanks for your detailed reply, that makes a lot more sense!
lets say i decide to make my own database secure, and still want to link to
this table in the other secure database. should i make my database secure by
using the wizard? this would mean my database and the other one have separate
workgroup files. the question is, how do I then link to the other database as
I'm still using the incorrect workgroup file?
Or is there a way to use an exisiting workgroup file (i.e. the one from the
other, already secure database) to make my database secure, so that we both
use the same workgroup file?
what would you advice?

Thanks again for your help, i really appreciate it!!

cheers
Barbara
 
Hi, Barbara.
lets say i decide to make my own database secure, and still want to link to
this table in the other secure database.

You'll want to use the same workgroup file for both database files. First,
join the secure workgroup as one of the Admins (or better yet, the group of
"SuperUsers," or whatever you may have that replaces the default Admins
group), then create a brand new database. Import everything from the
separate (unsecure) database into this new database. Now, every object will
be "owned" by this user, instead of the default "Admin" user. Archive the
unsecure database just in case you ever need to use it again, but you'll be
using this new, secure database from now on.

Link to the table in the first secure database, and create queries in this
new secure database based upon this linked table for necessary record
sources of objects. Give "Open/Run Database" permissions to the rest of the
users and assign whatever permissions necessary on the rest of the objects.

And keep that shortcut handy, so you don't have to worry about
authenticating whenever you're opening the unsecure databases. ;-)

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Back
Top