Tim L
Registered User.
- Local time
- Today, 15:06
- Joined
- Sep 6, 2002
- Messages
- 414
I have a database with the following design:
TableOne - Main records.
TableTwo - Subsidary Records (1)
TableThree - Subsidary Records (2)
TableFour - Optional Subsidary Records (1)
TableFive - Optional Subsidary Records (2)
There is a many-to-many relationship from TableOne to TableTwo and TableThree.
There is a one-two-one relationship from TableOne to TableFourand TableFive.
Enforce Referential Integrity is enabled for all relationships.
Cascade Update and Cascade Delete is enabled for all but the relationship from TableOne to TableFive. When I try to set Cascade Update (either alone or as well as Cascade Delete) I am informed that there is an:
"Invalid field definition 'id' in definition of index or relationship."
'id' is the long integer autonumber field (Primary Key) in TableOne, which has already been successfully linked to the other tables. I've checked the field properties in TableFive and its primary key field is set to Long Integer as well (NOT autonumber).
Any ideas why this is happening, and how the problem could be resolved?
Tim
TableOne - Main records.
TableTwo - Subsidary Records (1)
TableThree - Subsidary Records (2)
TableFour - Optional Subsidary Records (1)
TableFive - Optional Subsidary Records (2)
There is a many-to-many relationship from TableOne to TableTwo and TableThree.
There is a one-two-one relationship from TableOne to TableFourand TableFive.
Enforce Referential Integrity is enabled for all relationships.
Cascade Update and Cascade Delete is enabled for all but the relationship from TableOne to TableFive. When I try to set Cascade Update (either alone or as well as Cascade Delete) I am informed that there is an:
"Invalid field definition 'id' in definition of index or relationship."
'id' is the long integer autonumber field (Primary Key) in TableOne, which has already been successfully linked to the other tables. I've checked the field properties in TableFive and its primary key field is set to Long Integer as well (NOT autonumber).
Any ideas why this is happening, and how the problem could be resolved?
Tim