Subject | Re: [IBO] IBObjects 4.6 bc problems with local gdb files |
---|---|
Author | Ramil |
Post date | 2006-10-04T05:52:55Z |
Hello Remy,
Your problem is using FireBird2 with old client library.
Here is excerpt from Firebird 2.0(RC4) Release Notes:
Windows Local Connection Protocol with XNet
The transport internals for the local protocol have been reimplemented (XNET instead of IPServer).
With regard to the local protocol, the new client library is therefore incompatible with older servers
and older client libraries are incompatible with the Firebird 2 servers.
If you need to use the local protocol, please ensure your server and client binaries have exactly the
same version numbers.
--
Best regards,
Ramil R. Khabibullin khabibr@...
Your problem is using FireBird2 with old client library.
Here is excerpt from Firebird 2.0(RC4) Release Notes:
Windows Local Connection Protocol with XNet
The transport internals for the local protocol have been reimplemented (XNET instead of IPServer).
With regard to the local protocol, the new client library is therefore incompatible with older servers
and older client libraries are incompatible with the Firebird 2 servers.
If you need to use the local protocol, please ensure your server and client binaries have exactly the
same version numbers.
--
Best regards,
Ramil R. Khabibullin khabibr@...
>
>
>
>
>
> In IBObjects 4.6 Bc, TIBODatabase does not work when the Path property is
> set to an existing GDB file on the local maching and the Protocol property
> is set to cpLocal. When setting the Connected property to true,
> isc_attach_database() fails with an error code of 335544375, indicating that
> the database is unavailable. The GDB file itself works fine, even in
> projects using older versions of IBObjects.
>
> Setting the Protocol property to cpTCP_IP or cpNetBEUI instead of cpLocal,
> using the exact same filename for the Path property, works fine though. Is
> 4.6 Bc buggy, or is cpLocal not supported anymore?
>
> On a separate note, one of my co-workers found that when the Protocol is
> cpLocal, access to the database file is not thread-safe, whereas it is when
> using cpTCP_IP instead. We use IBO in multi-threaded applications, so we
> need all database access to be thread-safe.
>
> --
> Remy Lebeau
> Lebeau Software - Owner, Software Engineer
> http://www.lebeausoftware.org
>