Hello Helen,

yes, that is exactly what I'm doing. The table has 100-300 columns
depending on the machine's configuration, but in this cyclic updates
are only touched 4 or 5 of this colums. If the table has more columns
the problem occurs earlier, thats why I have written that the table
has many columns. The client is written in BCB6 with IBX as
DB-components. There are no triggers.
The clientcode creates every time a new TIBSQL-Object, a new
TIBTransaction-object, executes the query, commits, destroys the
TIBTransaction-object and finally destroys the TIBSQL-object.

Michel

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:

> Suppose there are 50 columns. Are you executing one update statement
> for each column, like
>
> update atable
> set column1 = :avalue
> where pk = 99
> COMMIT
>
> update atable
> set column2 = :bvalue
> where pk = 99
> COMMIT
>
> update atable
> set column3 = :bvalue
> where pk = 99
> COMMIT
>
> .... and so on...
>
> and you restart this cycle every 60 seconds?
>
> >When the machine is running there are normally only these updates
> >running on the DB.
>
> Can you show the client code that executes?
>
> Are there any update triggers on the table?
>
> ./heLen
>