allow duplicate values!

[ninja_imp]

updated relationship pic attached - many thanks for all your time and effort on this

 

[KeithG]

Do you have CustRef indexed, not allowing duplicates in the two tables? I don'
t see what is keeping them one to one.

 

[ninja_imp]

the relationships are all now one to many (see pic1) but it is still giving me the same bloody error (pic 2)

 

[ninja_imp]

CustRef is indexed in Tbl_Customers and is set as an autonumber. Is this right?

 

[ansentry]

Is ID set as the primary key for tblPublicationDetail?

 

[ninja_imp]

tblPublicationDetail is no longer part of the relationship and it is still giving the error!

 

[Rich]

Storing a calculated value in this way is incorrect anyway, a simple query will return the date due, it would also appear that you hve fields name Mon, Tues etc. which is a spreadsheet approach to db design. Look up some articles on normalisation/normalization

 

[MStef]

OK, it was what I was thinking.
The primary key in Tbl_CustomerBilling was
the cause of the error.
Now it's OK, look at Relationships, look at Tbl_CustomerBilling.

 

[ninja_imp]

It works! Your a star.

I had done this last night but the relationship had stayed as 'one to one' so i just deleted it, created a new one and bobs your uncle.

Many thanks for your help.

Just for future reference what was causing the problem?

 

[Rich]

You might also want to hide the real address you've posted in your image here

 

[ansentry]

I posted back your sample fixed 12 hours ago.

What has changed?