What causes an indeterminate join type? I use the lookup wizard link tbl-A to tbl-B to give me a drop-down pick-list for entering data in a table but when I look at the relationships window, it is labeled as an indeterminate join. Is that a problem or can it be ignored? If it is a problem, I am not certain what to do about it or even why it is a problem. This seems to be very basic but I guess the nuances are lost on me. Can anyone make any suggestions? I searched the forums for indeterminate joins but only turned up one entry. Thanks.
indeterminate joins
- Thread starter slrphd
- Start date
- Local time
- Today, 09:03
- Joined
- Feb 19, 2002
- Messages
- 47,313
This post didn't resolve your question - http://www.access-programmers.co.uk/forums/showthread.php?t=69428&highlight=indeterminate ??
Yes, this is a problem. When the join type is indeterminate, Jet will not allow you to specify that you want to enforce referential integrity. A relationship that does not enforce referential integrity is an accident waiting to happen.
Yes, this is a problem. When the join type is indeterminate, Jet will not allow you to specify that you want to enforce referential integrity. A relationship that does not enforce referential integrity is an accident waiting to happen.
Last edited:
- Local time
- Today, 08:03
- Joined
- Feb 28, 2001
- Messages
- 30,330
A join is indeterminate if one (or both) of the fields in the join have no indexes on which Access can base a decision about one-to-one or one-to-many relationships. If you have an index, it will be "unique" or "dups allowed" - and Access knows how to handle either one. Without an index, it has no clue.
Think of it as a decision table, fill in the boxes on both axes with unique and dupsOK, then you realize that unique x unique = 1-to-1, dupsOK x dupsOK is not allowed, and the other two boxes are 1-to-many or many-to-1. But if there is no index, there is no unique/dupsOK attribute so Access cannot decide whassup.
Think of it as a decision table, fill in the boxes on both axes with unique and dupsOK, then you realize that unique x unique = 1-to-1, dupsOK x dupsOK is not allowed, and the other two boxes are 1-to-many or many-to-1. But if there is no index, there is no unique/dupsOK attribute so Access cannot decide whassup.
