Link to a Secured DB table in an unsecured DB

[Tony_VBACoder]

With a unsecured Access 2002 SP1 database, how can I
create a link to a table that is in a Secured database
(has User-Level Security applied)?

 

[Albert D. Kallal]

There is absolute no problem with you doing as you ask.

however, the user(s) will have to be logged into the correct security
workgroup file.

If all, or some of the users have rights to use that secured database, and
then are logged into the correct security group..then they will have no
problems here.

However, if you are asking how can users get access to a table when they are
not part of the workgroup? You can't do this, unless you create some
workgroups, (or users) in the default workgroup file. However, if you modify
and change the default workgroup file, the it is not default much
anymore...is it?

So, as long as the users are logged into the correct workgroup file, then it
don't matter if the current database is secired, or not. What ONLY matters
is they are logged into a workgroup that gives them permsisions..

However, if you are asking if this can work when they are not logged into
ANY workgroup file that DOES NOT have permissions...then no...you can't do
that (and, if you could....what use would secirty be!!)

 

[Tony_VBACoder]

Albert, thanks for the reply...

From what you said, I want to make sure I understand you
correctly...you are saying that I will not be able to
create a link in the Unsecured Database to the table in
the Secured Database without first having the Unsecured
Database converted to a Secured Database because this
newly secured database would need to use the same
Workgroup (.MDW) file as the Secured Database?

 

[Joan Wild]

Albert, thanks for the reply...

From what you said, I want to make sure I understand you
correctly...you are saying that I will not be able to
create a link in the Unsecured Database to the table in
the Secured Database without first having the Unsecured
Database converted to a Secured Database because this
newly secured database would need to use the same
Workgroup (.MDW) file as the Secured Database?

Alternatives - Give the Users Group in the secured database Read Data
permission on the table you need to link to, and open permission on the
Database. The unsecured database will be able to link to the table. The
only problem is that anyone will be able to open the database and link to
that table, but they won't be able to do anything else.

Depending on what you do with the table once it is linked, you can use the
privDBEngine object to connect to another database (secured with a different
mdw). Details in section 46 of the FAQ.
http://support.microsoft.com/?id=207793