# 2962 Foreign Key Constraint Violation Errors are Indicating the Incorrect Table Names

---

It seems to me that the error message for error #1004 is not completely correct. At the moment, if a constraint is violated on table <TableName>, the message is:

ElevateDB Error #1004 The foreign key constraint <ConstraintName> for the table <*TargetTableName*> has been violated (The foreign key <Value> does not match any existing primary or unique key in the table <TargetTableName>)

But I think it should be:

ElevateDB Error #1004 The foreign key constraint <ConstraintName> for the table <*TableName*> has been violated (The foreign key <Value> does not match any existing primary or unique key in the table <TargetTableName>)