hopemedmike wrote:

>
> I've been working with databases on a firebird server in my office. I
> recently moved the firebird server from my office in boston to an
> office in NJ. Now when I run the client program on my computer, I can
> connect to the databases on the server with no problem. The problem
> lies in keeping the client program connected to the databases. If the
> program sits idle for more than a few minutes with no database
> activity, as soon as you go back to using the program, the connection
> is lost. This is obviously a network issue, as opposed to a
> firebird/interbase issue, but i was wondering if there were any
> tricks i coud use to aleviate the problem. One thing i noticed with a
> different client program which continually disconnects and reconnects
> to the databases, is that the program never loses its connenction.
> Perhaps merely having the database activity keeps it connected,
> whereas merely sitting there idle causes the connection to be lost.
> If anybody has any possible expananations to, or solutions for this
> problem, please let me know.
>

You are right.They are using timer to periodically polling database with
simple select first 1 from somethable or another quick-returning query.
This way Firebird server still think that this connection is alive
becouse there is a limit of idle connection time in Your Firebird
configuration:
from firebird.conf :

"
# ----------------------------
# Client Connection Settings (Basic)
#
# Seconds to wait before concluding an attempt to connect has failed.
#
# Type: integer
#
#ConnectionTimeout = 180
"

Merry Christmas

Best Regards
Boguslaw Brandys