[Firebird-odbc-devel] Deadlock using ADO

[Daniele Barzotti]

Dear,

I'm using the Firebird 2.1.3.18185 with latest RC1 release of ODBC.
My VB6 application use ADO to access to DB.
All works fine but I have this strange problem.

My App is a client-server and when the server wrote to a table, informs
all clients, and they requery their recordsets that points to the same
TABLES or QUERY.

In some circumstances, when I doing this requery (or a simple Open) the
instruction locks and freeze the application.

How can I solve this?

Regards,
Daniele.

[Daniele Barzotti]

Post by Daniele Barzotti
Dear,
I'm using the Firebird 2.1.3.18185 with latest RC1 release of ODBC.
My VB6 application use ADO to access to DB.
All works fine but I have this strange problem.
My App is a client-server and when the server wrote to a table, informs
all clients, and they requery their recordsets that points to the same
TABLES or QUERY.
In some circumstances, when I doing this requery (or a simple Open) the
instruction locks and freeze the application.
How can I solve this?

I go a step ahead.
I disabled transaction wait with NOWAIT=YES and now at the statement
that cause the lock I receive:

"lock conflict on no wait transaction deadlock"

It means that there is an already open transaction?
The driver opens a transaction for every SQL statement I do or only when
I open it explicitly with Connection.BeginTrans()?

Regards,
Daniele.