referential integrity, control 1-M, 1-1

[Ronze55]

Hi all,

I would like to use the referential integrity functions of ms access however I am having some difficulties controlling the options.

I have a few relationships between two tables which are 1-1 however when I pick cascade update, or cascade delete access makes them into 1-M

how can I control this option?

thanks in advanced,
Ronze

 

[Craig0201]

If the tables are truly 1 - 1 then they could be put in the same table. There is no need to separate them.

 

[Ronze55]

how can I tell access they are truelly 1-1 and not 1-M?
I should mention data has not been added yet

thanks
Ronze

 

[Crowley16]

if they are in different tables, access assumes they are not truely 1-1

--------------------
Procrastinate Now!

 

[Ronze55]

is there anyway to limit the number of updates per relation then?

ronze

 

[Crowley16]

I think you should be able to implement 1-1 and retain referential integrity...

have a look at the 2 tables, is there something in one that suggests anything other than 1-1?

try to look for a logical constraint in one that would not allow a record to be deleted, while in the other table, there's no such constraint...

--------------------
Procrastinate Now!

 

[Ronze55]

possibly in the foriegn keys. I'll look into that and let you know

thanks!
ronze

 

[pbrodsky]

If they are truly 1-1, shouldn't they have the same primary keys?