At 10:20 AM 28/11/2003 +1100, Alan McDonald wrote:

>I think you need to make sure that all clients connect to the server using
>the identical connection string too.

This is a corruption issue for IB 6 but Firebird won't allow clients to
connect if the path portion of the string doesn't match the first
connection's path string.

For Elena's benefit - this was an old InterBase bug that got fixed very
early in Firebird's history. It was never fixed in InterBase 5.6 or 6.0.x
(don't know about 6.5 or 7), so IB had/has this time-bomb built into
it. The kind of corruption you get from this bug needs major, specialist
repair.

Elena hasn't reported any explicit connection refusals but in one message
she did say the problem occurred if the user had been away from the desk
for a while. Now, it could be that a connection has timed out and the app
is reconnecting with a mismatched string, FB throws the exception.

Now, the application does not appear to be handling dpb exceptions at all -
hence the looping error dialog - so the "bad connection string" issue can't
be ruled out. It appears the application was written in IBX for connecting
to an IB 6 server, so it could be that the connection string issue is now
rearing its head...

The looping exception dialog alone is enough to indicate that the software
supplier has some bug-fixing to do, regardless of what is actually giving
rise to the exceptions.

Elena also mentioned that she installed "the Firebird client tools" on all
of the workstations. I meant to ask about that. I wonder what client
tools users would need, to warrant this risk.

heLen