Would you mean an “Indeterminate” relationship? That is just what you need to be getting into this instance.

Would you mean an “Indeterminate” relationship? That is just what you need to be getting into this instance.

sanders720 (Programmer)What is an relationship that is intermediate? We have two tables

Once I drag InquiryNo through the very first dining table towards the 2nd, I have an Intermediate relationship. The thing I really would like is a single to relationship that is many.

Assistance with this really is greatly appreciated.————————————————————JimHorton (Programmer)For a one-to-many relationship, you must have one of several areas be a distinctive industry, often this is a main Key. the other industry will never be unique, but it is good training to at the very least index it.

In your tables, the initial industry should really be InquiryID in the 1st table, and Customerid should always be a foreign key to your clients dining table (maybe not shown in your example–I’m https://datingranking.net/match-review/ simply mentioning it on a tangent). You will connect to the inq. date dining table.

Nevertheless it looks such as the very first dining table can be put up with a compound key–Cust id and inq.#, that is okay, then again you will need to place both custid and inq# when you look at the 2nd dining table, and then make the hyperlink on both those industries. This will be okay, but I would suggest the Inquiry # when you look at the first table be unique across ALL inquiries–not simply with this client id.

Each one for the above will be able to work however–the unique INq#, or perhaps the mix of Custid and inq#.–Jim————————————————————sanders720 (Programmer)There are now likely to be 5 tables, but i will be hoping to get three working first.

Client is related from another database, where consumer is keyed. The fields are. CustomerIDCustomerStreetAdress IICityStateZip

One other two tabes are mentioned formerly.

I would like to influence the connected dining table so far as updating customer / prospective customer information for that application, along with that one. To put it differently, the info is entered as soon as, either in spot. The other two tables define this application. We included CustomerID into the 2nd table and nevertheless got an Intermediate Relationship. WHAT EXACTLY IS AN INTERMEDIATE RELATIONSHIP ANYHOW? And does the relationship be meant by it doesn’t work? I just wish to monitor numerous email address to your inquiry, and include the client to your connected dining table to be used into the other application aswell.

Once more, your help is valued.


An indeterminate relationship occurs as soon as the industry (or industries) it’s predicated on are not uniquely indexed either in regarding the tables. Then create the relationship, it will be one-to-many if you create a unique index (it doesn’t have to be the primary key) on InquiryNo in the table where it should be unique, and. (if you have a unique index in both tables, the partnership is one-to-one.)

If, in reality, InquiryNo just isn’t unique in a choice of regarding the tables, in that case your expectation is wrong. As an example, if you have got a given InquiryNo twice into the table that is first and 3 x when you look at the 2nd table, there’s no option to inform, by taking a look at the data, which record in the 1st dining table goes with which record into the 2nd. This is exactly why the relationship is “indeterminate”. Instead, you might conceive it that both documents within the table that is first along with three documents into the 2nd, but that is a many-to-many relationship, which relational database systems (including Access, SQL Server, etc.) do not help straight. (it is possible to express them by making use of an intermediate dining table, nonetheless.)

BTW, “indeterminate” relationships additionally happen if an individual or each of the tables is related from another database. That’s because Access can not know if the indexes that are unique continue to exist during the time it really starts the dining table. You might, for instance, produce the relationship within the linking database, then go in to the back end database and delete the index, making the partnership wrong. In such instances, you should determine the connection into the database that holds both genuine tables, and allow the linking database inherit it. (If both tables are not within the database that is same there is absolutely no option; the connection can simply be indeterminate.)

Warning Sign Submitted

Many thanks for helping keep Tek-Tips Forums free of inappropriate posts.The Tek-Tips staff will always check this out and simply take action that is appropriate.

Leave a comment