bill2janesoft@... wrote:

> I use direct odbc api call, and
> one connection handle (A) to create and fill the rows
> another connection handle (B) to read the rows, statement handle for reading was
> freed.
> both handles did not issue any transaction and lived for ever. I used connection
> handle (A) to drop the table.

Creating a table and using it without committing the transaction is an
easy way to shoot yourself in the foot. Similar story goes for actions
like adding a new column and trying to populate it in the same
transaction or many other mix of DDL and DML statements.

> Any idea for how to tackle this problem will be appreciated.

Keep DDL operations in separate transactions and you should be fine.

--
Milan Babuskov
http://www.guacosoft.com