Referential Integrity and Linked Tables

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Monroeski
    New Member
    • Aug 2007
    • 30

    Referential Integrity and Linked Tables

    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?
  • FishVal
    Recognized Expert Specialist
    • Jun 2007
    • 2656

    #2
    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.

    Regards,
    Fish

    Comment

    Working...