Trying to update a table with foreign keys causes a key violation error.

I am trying to update a table wihch has a single Primary key and a number of foreign key fields - the foreign key fields have properties of:  Required = No, Indexed = Yes (Duplicates OK) and Default value = NULL. When I try to UPDATE this table supplying the primary key and one or several of the foreign keys I get a Key violation error. If the FKs allow nulls, I am bemused why this should occur ? Any ideas anyone ?
The PK I am supplying id definitly unique.
If I dont supply any of the FKs I dont get a key violation and the table updates.
I am enforcing referential integrity between the primary and foreign key tables.

Tony
fester62DeveloperAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
fester62Connect With a Mentor DeveloperAuthor Commented:
I think I may have just figured the problem...and the clue is in the above! I have another table called OUstructures which defines a hierarchy of OU Codes. However, the primary table for OU Codes in tblOUCodes and any validation of OU Codes should always be done against this. For some reason, although whilst doing some work in the relationships window, I managed to invert the relationship between OUStructures and OUCodes, so that OUStructures became the Primary table.

In another case I set a default of '0' for a numeric key on the many side but did not allow this as a default value in the primary table.

Tony


Tony
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Connect With a Mentor Commented:
Remove NULL as the 'Default Value'
By definition - they will be Null unless you populate them

Also ... are you *sure* that you have INexed = Yes (Duplicates OK) for all FK's ?

mx
0
 
Mark WillsConnect With a Mentor Topic AdvisorCommented:
There is a reasonable probability that the columns being supplied are not NULL, they may well be an empty string, or zero length string which is not the same as NULL and will try to populate. That is the typical reason when it works if you do not supply the column. So, check those columns, and make sure they are in fact NULL.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
fester62DeveloperAuthor Commented:
MX: yes all FK fields are set to Yes(Duplicates OK) in primary table; I have re-checked.

Tony
0
 
fester62DeveloperAuthor Commented:
mark_wills: I am only supplying non-null values at present, so there is no opportunity for getting "" mixed up with NULLs. I am aware of the difference.

I have tried a number of INSERTS using different combinations of the fields in the Primary table (there are some 30 odd altogether). At present it seems to fail on one particular field, that happens to be called 'OU Code'. The INSERT statement is as follows:

INSERT INTO tblResources ([GPN], [FirstName], [LastName], [FTE], [PAC], [OUCode], [DataSource]) VALUES ('HRID11112', 'test 1', 'test 2', 1, 1, 'GUBY', 'M');

The field has the properties in the update table and Related table as shown in the attached.

tony



OU-Code-properties.bmp
0
 
fester62DeveloperAuthor Commented:
Btw, I have tried the above statement omitting the OU Code and it is successful, so it cannot be due to any other field. I have a similar problem with other FK Fields (not included in the above INSERT), but they are all defined in a similar way to the above.

Tony
0
 
fester62DeveloperAuthor Commented:
Attached relatonship definition:
OU-Code-relationship.bmp
0
 
Mark WillsTopic AdvisorCommented:
Hi tony,  Good detective work... cannot see anything untoward, you have allow zero length, and it is not required... You wouldnt happen to have a test database or something that does not compromise security / IP etc that you would care to share ?
0
 
fester62DeveloperAuthor Commented:
Thanks for your comments, often just posting stuff here makes you go through and retest things you thought you had made good, but sometimes havent!

Part of the solutuion was prompted by mark_wills comments re: checking what values, nulls, "" etc are being supplied, so I will award half the points there. The rest nobody could have figured out until I posted the last screenshot. Thx Mark.

Tony
0
All Courses

From novice to tech pro — start learning today.