By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,700 Members | 1,458 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,700 IT Pros & Developers. It's quick & easy.

Referential Integrity and Linked Tables

P: 30
We are working on putting together a network of Access DBs for a few projects at work. Our plan was to have a "Master" DB with, for instance, a table that has a list of departments and their passwords, then have all our other DBs link to that table so that any changes in the Master table will automatically update across all the rest. The problem with this strategy, we just realized, is that when you try to set up a relationship between a table and a linked table, you can't enforce referential integrity. Any way to get around this?
Feb 20 '08 #1
Share this Question
Share on Google+
1 Reply

Expert 2.5K+
P: 2,653
Hi, Monroeski.

If you use read-only field (Autonumber fits best) as PK, then you will never need cascade update.
And you may use a simple "find unmatched" query to simulate cascade delete. You just need to plan when and where to run it.

Feb 20 '08 #2

Post your reply

Sign in to post your reply or Sign up for a free account.