Re: RecordChangeComplete and Primary Key constraint
From: Olivier Matrot (olivier.matrot_at_online.nospam)
Date: 09/29/04
- Next message: Asmus Wanke: "Crash with ADO15.dll in Access XP"
- Previous message: Dennis Forbes: "Re: ADO seemingly terminating batch"
- In reply to: Olivier Matrot: "RecordChangeComplete and Primary Key constraint"
- Next in thread: Kevin Yu [MSFT]: "Re: RecordChangeComplete and Primary Key constraint"
- Reply: Kevin Yu [MSFT]: "Re: RecordChangeComplete and Primary Key constraint"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Sep 2004 16:34:43 +0200
More informations on this.
I'm using the lastest MDAC version (2.8).
I'm using the OLEDB SQL Server provider.
The status property of the RecordSet is 1 (adRecNew).
I'm actually trying to insert a new record in a table. This new record
violates the primary key constraint.
"Olivier Matrot" <olivier.matrot@online.nospam> wrote in message
news:egrRa7gpEHA.1152@TK2MSFTNGP11.phx.gbl...
> Hello,
> Correct me if I'm wrong but it seems that the status of a field that is
> underlying a primary key constraint is not set to an ERROR value in the
> the RecordChangeComplete Event when the record in error violates the
> primary key constraint.
> My tests shows that only the pError parameter is set.
>
> The problem here is because pError is specific to the OLE DB Provider
> used, there is no simple way to determine that a constraint Error has
> occured.
>
>
> TIA.
>
- Next message: Asmus Wanke: "Crash with ADO15.dll in Access XP"
- Previous message: Dennis Forbes: "Re: ADO seemingly terminating batch"
- In reply to: Olivier Matrot: "RecordChangeComplete and Primary Key constraint"
- Next in thread: Kevin Yu [MSFT]: "Re: RecordChangeComplete and Primary Key constraint"
- Reply: Kevin Yu [MSFT]: "Re: RecordChangeComplete and Primary Key constraint"
- Messages sorted by: [ date ] [ thread ]