That means there is a foreign key constraint you are violating.
Example:
say you have a USERS table and an ORDERS table. The primary key in USERS is
user_ID and ORDERS has a user_ID field (but it's not the primary key). IF
there is a foreign key constraint defined that says you can't have an order
without a valid user_ID then you must enter a valid user_ID when inserting
an order.
If you try to enter NULL for user_ID you will get the error below.
You might be tempted in your case to disable the constraint to make the
error go away, but don't.
+-----------------------------------------------+
Bryan Love
Macromedia Certified Professional
Internet Application Developer
Database Analyst
Telecommunication Systems
[EMAIL PROTECTED]
+-----------------------------------------------+
"...'If there must be trouble, let it be in my day, that my child may have
peace'..."
- Thomas Paine, The American Crisis
-----Original Message-----
From: CF_JONNY [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 18, 2002 3:48 PM
To: CF-Talk
Subject: SQL>>>HELP QUICK!
What does this mean?
Error Diagnostic Information
ODBC Error Code = 23000 (Integrity constraint violation)
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert the value NULL
into column 'athId', table 'blah.dbo.blah'; column does not allow nulls.
INSERT fails.
Do I need to set the Primary Key in SQL?
I cannot get the entry to give the auto number..
JON
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
