
Strange Behavior - ADO and SQL Server 6.5
Hi,
I have this table in SQL Server 6.5:
CREATE TABLE "dbo"."Lan_Valores" (
"ID_Item" "int" IDENTITY (1, 1) NOT NULL ,
"ID_Lan" "int" NOT NULL ,
"ID_Conta" "int" NOT NULL ,
"NoDocto" char (50) NULL ,
"Tipo" char (1) NOT NULL ,
"Historico" "text" NULL ,
"Valor" "float" NOT NULL ,
"INStamp" "timestamp" NULL ,
CONSTRAINT "PK_Lan_Valores_1__15" PRIMARY KEY CLUSTERED
(
"ID_Item"
)
)
And in a VB6 code, I insert values using this:
SQLEx = "insert into lan_valores (ID_Lan, ID_Conta, NoDocto, Tipo,
Historico, Valor) "
SQLEx = SQLEx & "values"
SQLEx = SQLEx & " ( "
SQLEx = SQLEx & IDLan & ", "
SQLEx = SQLEx & CamposVal(i).cpID_Conta & ", "
SQLEx = SQLEx & "'" & CamposVal(i).cpNoDocto & "', "
SQLEx = SQLEx & "'" & CamposVal(i).cpTipo & "', "
SQLEx = SQLEx & "'" & CamposVal(i).cpHistorico & "', "
SQLEx = SQLEx & "" & VerValor(CamposVal(i).cpValor) & ""
SQLEx = SQLEx & ")"
DataEnvironment1.ConnectionSQL.Execute SQLEx, , ADODB.adCmdText
It has been work very well for weeks, but now, I got:
Violation of PRIMARY KEY constraint 'PK_Lan_Valores_1__15': Attempt to
insert duplicate key in object 'Lan_Valores'.
I receive the same error if in other table with ADO Method ADDNEW
(I dont know who is inserting an existing KEY in the table? ADO or SQL
Server?)
I think its an ADO bug, but I dont know why its worked well for a couple of
weeks.
Someone has experienced this trouble?
Regards,
--
Hammett
http://www.*-*-*.com/