CK_(table) problem

[SBTBILL]

I'm getting a problem in writing to MS SQL tables. I get the message ck_(table) on inserts which I understand is telling me there is a constraint violation. I created the table and didn't add any constraints. It stops inserts or more.

Anybody seen this before?

Bill Couture
SBTBILL.COM

 

[Mike Lewis]

Bill,

Could you be more precise with the wording of the message. Is it literally "ck_(table)"? That doesn't sound like any error message I've seen.

Also, can you clarify which back-end database you are using. Different databases behave differently in terms of errors. You mentioned "MS SQL". Does that mean SQL Server, or what?

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[Olaf Doschke]

SQL Server does create constraints for relations but also if you simply set a primary key. Goto SQL Management studio, look into the constraints of that table and see how they are defined.

Bye, Olaf.

 

[JRB-Bldr]

"I'm getting a problem in writing to MS SQL tables. "

Did something work before and now it is not working?
Or is this new code which has never worked?

If this is a new problem for 'seasoned' code - what has changed?

If this is new code - have you run the code directly within the SQL Server to ensure that all the syntax, etc. is correct?

Good Luck,
JRB-Bldr

 

[SBTBILL]

Yes, this is Sql Server.

Right now it appears that the code is actually in a stand alone store procedure. The code had worked when sent via ADO from Fox. Still does.

The actual message is CK_event_log. Event_log is the name of the table being written to. Apparently the message is actually CK_ plus the table name. It isn't the SQL internal event_log as it is my table that is messed up. From what I have beem able to tell the message has something to do with constraints with in the table. However, this table has no constraints. It even allows nulls on all but the ID field. I use it to track when programs have run, when significant changes occur and the like. Because of this about the only thing done by code is to insert records.