Subject | Re: [firebird-support] Re: Odbc-problems2 |
---|---|
Author | Alexandre Benson Smith |
Post date | 2005-03-30T21:27:39Z |
poneyc wrote:
The SS version of FB open the file with exclusive access, it is to avoid
to connections to the same DB as if it was 2 different DB's, I can only
think of something wrong in the connection string that leads to diferent
string to resolve to the same physical file. Double check this...
Did you tried with the Stable version of ODBC driver (1.0.2.69) ?
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.5 - Release Date: 29/03/2005
>Thanks for the suggestions. I contacted the developer of the DelphiSorry, but...
>application and got the connection string. The connection string I am
>using is exactly the same as the connection string used by the thick
>client, and the problem still persists. It looks like this:
>
>dbhost.mydomain.com:D:\database\databasename.gdb
>
>As I said, I can connect through ODBC just fine to an instance which
>has no other connections, and multiple instances of the thick client
>can all connect at the same time, but I cannot connect through ODBC
>and get the "Connection failed! File database is in use by another
>process." error when trying to connect when any thick client instances
>are also connected.
>
>So, I'm still at a loss to explain this. It seems strange that
>multiple thick clients can all connect, and that I can connect through
>ODBC when no thick clients are connected, but that I cannot connect
>through ODBC when any thick clients are connected.
>
>Sorry to sound like a broken record, but once again, any more thoughts
>from anyone? Anything else I should be doing to track down the
>problem? Seems like it has to be something obvious I'm just missing.
>
>Regards,
>
>Poney Carpenter
>
>
The SS version of FB open the file with exclusive access, it is to avoid
to connections to the same DB as if it was 2 different DB's, I can only
think of something wrong in the connection string that leads to diferent
string to resolve to the same physical file. Double check this...
Did you tried with the Stable version of ODBC driver (1.0.2.69) ?
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.5 - Release Date: 29/03/2005