At 03:09 PM 23-04-02 +0200, you wrote:

>Thanks Paul.
>
>I try to explain my problem clearer. I make 5 'insert statements' in my main
>application.
>In a thread of my application i wait until the 5 'insert statements' are
>send to the database (jdbc).. then i make a commit

Why? I doubt that this is possible. A transaction has to work through
either a single connection to one database, or across connections to
multiple *different* databases. In the case of multiple different database
connections spanned by a single transaction, we have a thing called
"two-phase commit" to ensure that a commit takes effect across all
connections or gets rolled back across all connections.

In a single thread you need: a connection---a transaction---a bunch of
statements posted as pending----a commit or rollback to complete the
job. I've conducted some pernicious experiments (not with a Java client)
to convince myself that you really can't do it any other way.

>with the same database connection i used before. Have you any idea what the
>error message of the jdbc client means ?

Because I don't know any better, I'd say any error message coming back with
the word "bug" in it indicates that you might be running with a debug build
and indeed have encountered a known bug (whatever bug code 10019 might
be). Maybe it's just yelling at you because of a memory access violation,
rather than crashing spectacularly.

Helen

All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org ·
http://users.tpg.com.au/helebor/
_______________________________________________________