Results 1 to 4 of 4
  1. #1
    5 Star Lounger
    Join Date
    May 2001
    Location
    Patterson Lakes, Melbourne, Victoria, Australia
    Posts
    637
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Referential integrity (2000)

    In the front end is there any way of enforcing referential integrity with cascading updates & deletes between 2 tables from 2 different back end Dbs?
    Regards,
    Peter

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Referential integrity (2000)

    As far as I know, Access can only enforce referential integrity between tables physically residing in the current database. You can't set referential integrity if at least one of the tables is a link to a table in another database.

    So if possible, place both tables in the same backend database, and set referential integrity there (in the backend database; it is impossible to do it from the frontend database). Otherwise, you'll have to write code to create your own referential integrity in all forms used to edit data in the tables (in the BeforeUpdate, Delete, BeforeInsert events), but this is not failsafe, of course.

  3. #3
    5 Star Lounger
    Join Date
    May 2001
    Location
    Patterson Lakes, Melbourne, Victoria, Australia
    Posts
    637
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Referential integrity (2000)

    Thanks Hans. It's not possible in this case to have the tables in the same Dbs.
    Regards,
    Peter

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Referential integrity (2000)

    In that case, you have to handle all those cascades through code instead of Access handling it automatically.
    Charlotte

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •