In a relational database you create relationships by populating fields and then issuing SQL. If the join fields each have unique values then your relationship is 1:1. If one has multiple values (eg a foreign key) you have 1:n. If both have multiple values you have m:n. I do have tables with the latter but almost always this is not helpful, so you use intersection entities as Urn has said.
The important thing to understand is you do not create these relationships by Access relationships. Access relationships are a mechanism to a) help certain wizards and Front-end processes (eg the QBE Designer), and b) enforce constraints. It is a fundemental rule of the relational model that data and relationships are exclusively represented by table values. No under-the-covers shenanigans are allowed. Access obey this rule.
This is really interesting stuff, and can I ask what you want to do with cardinal numbers? And are you looking at the sequencing of numbers, infinite / finite number sets??
The above posts are correct that establishing relationship will be tricky, and it would help to know your expected outcomes to provide more details.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.