Access Relationship showing 1 to 1 not 1 to infinity please help

[Guest]

I the relationship link is not showing the infinity symbol it is showing 1 on
both sides. So I can't load multiple entrys with the same ID

 

[David F Cox]

You should be able to change the join type by double clicking on the join
line. It brings up a pop-up window.,

 

[Guest]

Thank you for the post, I probabley did not give enough info. I have just
built this query however due to there only being one (1) on each side I can't
add entrys more than once with the same primary key. When I click on the
relationship line it changes the arrow directions but does not appear to give
the infinity symbol. I

 

[BruceM]

What are the fields you are trying to join? For a one-to-many you need a
primary key (PK) field (unique value) in the table on the "one" side of the
relationship, and a foreign key (FK) field in the table on the "many" side.
The PK is established in table design view, but the FK is established by its
relationship to the PK. There is no command to establish a FK field as
there is with a PK field.
If the PK field is autonumber, the FK field must be Number (Long Integer);
in all other cases the PK and the FK must be the same data type. Using the
example of a customer calls database, it would go something like this:

tblCustomer
CustomerID (PK)
CustomerName
other fields such as Phone that are specific to the customer

tblCalls
CallID (PK)
CustomerID (FK)
CallDate
Other fields specific to the call

The one-to-many relationship is between the two CustomerID fields. The
fields don't need to have the same name, but it may make it easier if they
do. When you establish the relationship, tick the check box for Enforce
Referential Integrity.

If this doesn't address the question you will need to provide more details.

 

[Guest]

Resolved Thank You - The primary keys in both tables were the same. do ooh!

 

[John Vinson]

I the relationship link is not showing the infinity symbol it is showing 1 on
both sides. So I can't load multiple entrys with the same ID

This will happen if there is a unique Index - such as a Primary Key -
on the ID field in both tables. What are the two tables? What is each
table's Primary Key? What fields are you using to join them?

John W. Vinson[MVP]