Here's another one that should be fixed. The current code
checks for specific variations in filename under SuperServer
on Windows. I don't know why the server doesn't just lock
the database when it opens it.


Bug #113462, was updated on 2000-Sep-02 19:34
Here is a current snapshot of the bug.

Project: Firebird
Category: Connectivity
Status: Open
Resolution: None
Bug Group: Confirmed
Priority: 5
Summary: Win 32 accepts ambiguous TCP/IP connect strings

Details: Win 32 allows clients to connect with either
servername:c:<localpathname> or servername:c:\<localpathname>. If
connected clients have connected with a mixture of these string formats,
the database is treated as if it were multiple databases and corruptions occur.