How to access a linked table from one secure database to another

  • Thread starter Thread starter ashwinv
  • Start date Start date
A

ashwinv

Hi,

I have 2 databases being used by 2 different groups in the company.
Both of these databases are secured (I just secured the 2nd one) and
have their own seperate workgroup files. There are links from the 1st
database to tables in the second.

After I secured the 2nd one, these links no longer work. I have tried
to create the same user and password in both the databases and even
that did not work. Is it even possible to administer these databased
using 2 workgroup files or do I need to keep just one workgroup with
the list of users of both the databases and assign permissions
accordingly. Does it mean that I have to create a new database and
import all objects from both the databases and then create the
workgroup and assign permissions accordingly or is there another way?

Any help is deeply appreciated.

Thanks,
Ashwin
 
Creating the same user and password isn't the way.to go (and if it were,
you'd want to create the same username and PID (not password)).

You need to create a group that is common to both mdw files. Make sure you
use the exact same name and PID string in both. Now that this group is
common, any users you add to the group will get the permissions for that
group. So just add the permissions on the group that are needed to read the
tables.
 
After I secured the 2nd one, these links no longer work.

Then it's working like it should. Imagine if I could link to *your* secure
database from *my* secure database but we used two different workgroups to
secure our databases. If that were the case there wouldn't *be* any security.

Is it even possible to administer these databased
using 2 workgroup files

It can be done but it would be painful.
Does it mean that I have to create a new database and
import all objects from both the databases and then create the
workgroup and assign permissions accordingly or is there another way?

Pick the workgroup you want to keep, join it and create a new database and
import the objects from the database that was secured with *the other*
workgroup (after you've unsecured it of course) and apply permissions to
these objects in the new database.
 
Back
Top