Have no idea why this does not work....... please help

[Guest]

Good Morning.

I hope someone can help me. I have 4 tables containing data which all
relate to the same sales order number.
Table 1 - Sales order
Table 2 - order details
Table 3 - budget hours
table 4 - sales order authorisation

All contain the sales order number as all the tables hold details relating
to each sales order.

What I want to know is if one table i.e. sales order, can have a one-to-many
relationship as well as 2 one-to-one relationships? I can get a query which
joins sales order table and order details table to update using cascading
referential integrity. This is great, but then when I add the other two table
using 1 to 1 relationships to the sales order table, it all goes pear shaped!

Any advise would be greatly appreciated.

Thanks in advance.

 

[[MVP] S.Clark]

Your description was doing so well, but then went pear shaped at the end.

Does it show an error message, does Access crash, do two ducks fly across
the screen? What is pear shaped exactly?

--
Steve Clark, Access MVP
FMS, Inc.
Call us for all of your Access Development Needs!
1-888-220-6234
(e-mail address removed)
www.fmsinc.com/consulting

 

[Marshall Barton]

I hope someone can help me. I have 4 tables containing data which all
relate to the same sales order number.
Table 1 - Sales order
Table 2 - order details
Table 3 - budget hours
table 4 - sales order authorisation

All contain the sales order number as all the tables hold details relating
to each sales order.

What I want to know is if one table i.e. sales order, can have a one-to-many
relationship as well as 2 one-to-one relationships? I can get a query which
joins sales order table and order details table to update using cascading
referential integrity. This is great, but then when I add the other two table
using 1 to 1 relationships to the sales order table, it all goes pear shaped!

The difference between one to one and one to many is that in
a one to many relationship, the many table uses a foreign
key to refer to the related record in the one table. In a
one to one relationship the linking field is the primary key
in both tables.

AFAIK, Cascade can not manipulate primary keys.