Hi Lucas, long time, no auction!

I don't think this is the reason for your insert/update problem, but one
possible way to be allowed one insert and no update, is to have a
trigger that sets one or more of the fields in Keylinks (or possibly
MasterLinks). In such cases, the identifier for the row is known at the
server, but not at the client and any update is impossible.

I also suspect an update/insert to be impossible if you have two or more
transactions running simultaneously and insert into a table that has a
trigger updating a common row in another table.

The one thing that these two thoughts have in common, is that they
involve triggers. So, do you have any triggers in your database? I take
it that you've set keylinks to something unique?

Set

Lucas Franzen wrote:

> I just stumbled across that again.
> I added a TIB_Cursor which was meant for inserting / updating some data,
> but I forgot to set the RequestLive property to true.
>
> Anyway:
> I'm able to do one insert/update. I do just get an error when I do it
> the second time. I don't understand why I can perform one (and just one)
> DML statement when I excpect not to be allowed to perform any.
>
> Any clues?
>
> Luc.