View Full Version : Linked Tables


CEB
01-27-2005, 08:15 AM
Hi folks,
I have a table and I want most of the fields available to others. I also want the other users to be able to add fields to the table (not the master but theirs). Here's an example to explain it better:

MasterTable contains the following fields:
Name,Address,Phone,Training,Checks.

I want the Users to have a linked table with access to:
Name,Address,Phone

I also want the users to be able to add their own fields like:
Date of Birth etc. to have a table that is linked to Master but they can change some fields.

Any suggestion would be much appreciated.
Thanks,
Colin.

Pat Hartman
01-27-2005, 12:39 PM
This is not a good idea. Shared databases should not contain objects made/chaged by users. The users of the database should only be able to work with data.

If you were to use a shared database to hold the common table and individual databases for each user, they could of course add their own stuff, if you allow it. There would be no way to enforce refenterial integrity between the local table and the linked table so it would be quite easy for the two tables to get out of sync.

Why not just add the requested fields to the main table? You could separate the private fields into a separate table so that you can use security to prevent most users from accessing that data.

CEB
01-27-2005, 12:59 PM
Thanks alot Pat,
I'll have to think about this further. Adding extra fields for the other users is definitely a way to go. Is there a way that they can only see what fields I wish them to see or do I have to break the table into seperate tables? I have already a lot of records in there and there is no primary key. I could give all the records unique numbers if I have to split it in to different tables though.
Thanks again,
COlin

Pat Hartman
01-28-2005, 05:16 PM
Is there a way that they can only see what fields I wish them to see or do I have to break the table into seperate (sic) tables? Jet does not enforce security at the column level. You would need to do this in your database by splitting the table in two. You would still need to enforce Access' workgroup security to limit access to the separate tables.

As long as you have a combination of public and private data in the same database, you don't have any alternative than Access/Jet security.