Re: Row cannot be located for updating
From: Hans van Leth (hans.v.l)
Date: 01/06/04
- Next message: Jeff: "ADODataset\Looping"
- Previous message: Arnie Mauer: "Re: does CommandTimeout takes effect?"
- In reply to: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Next in thread: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Reply: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 6 Jan 2004 15:22:15 +0100
Hi Brian,
thanks for taking the time to answer.
It is a simple table I am trying to update, not a join.
The insert/update trigger pulls information from other tables and populates
some fields of the table being inserted/updated which makes for ADO to not
being able to find the just inserted record back.
The solution I was hoping to find was to inform ADO which field(s) are the
key to the table. I know this is possible, but cannot find out how this is
done from D7. Without this, ADO will default to taking *all* fields as the
key and stuff these in the SQL WHERE clause it constructs on the fly.
Thanks again for any clues (if any!).
Hans van Leth.
"Brian Bushay TeamB" <BBushay@Nmpls.com> schreef in bericht
news:vn6kvvgu7hp7vddua6fsv3i2a2lprkq7gc@4ax.com...
>
> >I've read some time ago in this NG (I believe) that you can limit the ADO
> >where statement construct by informing the ADO recordset about this
primary
> >key (or rather: dropping the other fields). I have searched this NG and
also
> >Tamarack but cannot find this message anymore.
> ADO has a Unique Table property to specify the table from a Join that gets
> updated.
> Also in your Trigger add
> Set Nocount On
> at the begriming of the trigger.
>
>
> --
> Brian Bushay (TeamB)
> Bbushay@NMPLS.com
- Next message: Jeff: "ADODataset\Looping"
- Previous message: Arnie Mauer: "Re: does CommandTimeout takes effect?"
- In reply to: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Next in thread: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Reply: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|