Sharing tables between secured Databases

[Leif]

I have a user-level secured Access 2003 database. I'm creating a new user-level secured Access 2003 database. They have different workgroup security files (.mdw).

I'm trying to use a table link in the new database to a table in the old database.

According to what I read if I used the same group name, organization name, and PID for the group in both databases then the generated SID (Secured ID) for both databases should be the same. I tried adding a group in the new database with the same Group name and PID as the old database. Success! However, that group has more permissions to tables then I want in the new database. So I created a new group in both the old and new databases, both with the same name and PID (the organization name is the same). Failure!

Any suggestions?

Thanks,
Leif Eriksen

 

[apr pillai]

Why you need two .mdw files?

 

[Leif]

The two databases have some of the same user and some that are different users. Also, some of the tables and forms, although different in the two databases have a name overlap. So, I don't think it is practical to use one mdw.

For everyone's information, a poster by the name of Joan Wild, in another forum, had the answer for me. The problem is the group I was trying to use did not have open rights for the database.

 

[smig]

first thing is to split your db to FE/BE
BE - BackEnd - data
FE - FrontEnd - application

you link both applications to the same BE. BE should not be group secured but password secured. you put the password when you link the FE. users should not use this password and don't neet to know it.

 

[Leif]

I've tried the FE/BE idea. Its slows access down. It also complicates updates. This is a common suggestion, I've heard it many times, but after working with Access for 7 years I've found this is not a good idea.

 

[CBrighton]

Leif, it slows access down when it is having to constantly open and close connections.

If you were to open a connection when the first form opened and keep it open until the database is closed then there should be minimal slowdown.