database table relationships

  • Thread starter Thread starter bing
  • Start date Start date
B

bing

The tables in our database application have referential integrity, and mostly
linked to the primary table. Somehow the relationship links dropped a couple
of weeks ago during some modification/importing data process. We did not
notice that. So, I assume if I delete data from primary table, the cascade
update/delete did not work.
I am asking for help here, what are the possible reasons that tables could
drop the relationship? Could anyone give me some suggestions of how to fix
the problem?
 
I have experianced this in the past during imports. For some reason access
allowed a duplicate Primary key value, wich caused my relationship to break.
I found the duplicated value by running the find duplicate value query
wizard, deleted the duplicate, and rebuilt the relationship. Then I made a
query that check to make sure there were no duplicates in the table I was
importing to before it sent the new data. Hope this helps.
 
Thanks, Ryan. I will try that.

Ryan said:
I have experianced this in the past during imports. For some reason access
allowed a duplicate Primary key value, wich caused my relationship to break.
I found the duplicated value by running the find duplicate value query
wizard, deleted the duplicate, and rebuilt the relationship. Then I made a
query that check to make sure there were no duplicates in the table I was
importing to before it sent the new data. Hope this helps.
Click to expand...
 
you _CANNOT_ have ANY referential integrity if you use Linked Tables.

Sorry.

-Aaron
 
You cannot enforce referential integrity between tables in different
databases, but you can enforce RE between the tables in a single (back end)
database. If the FE is linked entirely to that BE database then referential
integrity can indeed be enforced.

you _CANNOT_ have ANY referential integrity if you use Linked Tables.

Sorry.

-Aaron
 
Back
Top