At 11:44 AM 13/05/2006, you wrote:

>Hi,
>
>I got following error on a DML operation (I think it was INSERT
>operation but I am not sure it might be UPDATE, SELECT or even a DB
>procedcure call - I did not notice at that time).
>
>"Lock conflict on no wait transaction deadlock."
>
>At the time when I got this error, I was the only person who was
>connected to the firebird DB.
>
>I think the error should come when there are at lease 2 users connected.

No, not quite. Locking conflicts occur between concurrent
transactions. Transaction <> user.

>Does anybody has any information about how this can be resolved.

Yes, find out why your application is doing stuff in separate
transactions. It's not necessarily a reflection of a fault in the
design, though. It might quite intentional, to ensure that all of
the work happens within a single transaction. If so, then it will be
easy to provide for the conflict case by catching the exception and
directing the user to do the right thing.

>I dont know whether this has to do anything with "less RAM", When I
>increased the RAM (from 500 Mb to 1 Gb) I could not replicate this.

No, having insufficient RAM doesn't cause locking conflicts and
adding more RAM doesn't cure it.

./heLen