no, it's a "unique-user" application, local environment, and the time that
they are in the form is very short.
The time a transaction is open is very short, the only time is large is the
connection to the database:

8:00: open connection
8:05: begin trans
8:07: commit
9:05: begin trans
9:10: commit
...
14:00 shut down pc, without closing connection in client, the server asks if
they want to close the active connection, and they say yes.

i could do a close connection after every commit, and a open conn before
beginning transaction, but in this way, the application will be slower.

What do you think?

Lots of thanks

Daniel Aut
daniel.aut@...

----- Original Message -----
I understand that this is not an answer to your question, but your
description (below) brings a question.
Are you saying that you have an application, that can allow a transaction to
be "open" for extended periods of time, like, for instance, the user starts
the application (opens connection), goes to a form (starts a transaction),
goes to lunch, comes back 1 hour later, closes the form (ends transaction)
??
If so, then this is an extremely poor design, especially in a multi-user
environment.

Best regards,
Fred Wilson
SE, Böwe Bell & Howell
fred.wilson@... <mailto:fred.wilson@...>

-----Original Message-----
Hi,
i'd like to know what happens if i shut down the server (a Win98 pc) while
there is an open connection, but this is not in transaction, i mean it was
commited before.

Will give more details:
i have an application, that connects to firebird (local server) when it
begins. Every time it opens a form, it begins transaction, and when it
closes a form, it commits transaction. When the application closes, it
closes the connection.
The users shut down windows, but not application, (there isn't forms opened,
therefore the transaction is closed, but not the connection).

Is there any problem with all that?

Thank you!

PD: Sorry about my poor english