Subject | Re: [firebird-support] How to connecto to an embedded Firebird? |
---|---|
Author | W O |
Post date | 2011-07-09T22:26:16Z |
Hello Helen
That mean that I cannot connect to a database without an ODBC driver?
I want to make an application portable, without installation. That is very
easily done with FoxPro native tables (.DBF tables)
The user insert his/her pen-drive and the application works.
Is impossible to do the same thing with Firebird embedded?
Thanks in advance.
Walter.
That mean that I cannot connect to a database without an ODBC driver?
I want to make an application portable, without installation. That is very
easily done with FoxPro native tables (.DBF tables)
The user insert his/her pen-drive and the application works.
Is impossible to do the same thing with Firebird embedded?
Thanks in advance.
Walter.
On Sat, Jul 9, 2011 at 4:41 PM, Helen Borrie <helebor@...> wrote:
> **
>
>
> At 12:24 AM 10/07/2011, W O wrote:
> >Yes, the message said: "connection error"
> >
> >I can connect if I have an ODBC driver installed, but with "embedded" it
> >would be not necesary, right?
>
> Wrong. "Embedded" does not embed any drivers.
>
> It consists of a Firebird engine (with all its ancillary components in the
> right places) and a Firebird client that exposes exactly the same API hooks
> that the regular client does. (In fact, you can use that embedded client to
> connect to a full server!) Whatever driver (middleware layer) you would use
> to pass API call traffic from your app to a regular client, you would use
> the same for the embedded client.
>
> With Flamerobin you don't need an external driver because it is written in
> C++ and has been compiled with all its connectivity on board, using IBPP as
> its middleware.
>
> Understand what Sean is saying to you about the "bitness" of the client
> layers. Even if you are running a 64-bit Windows, you will need
> 32-bit-everything for your app because Foxpro only does 32-bit.
>
> Also check, via the firebird-odbc-devel list, not this list, whether you
> still need to rename fbembed.dll to fbclient.dll (or even gds32.dll) with
> the ODBC driver version you are using.
>
> ./hb
>
>
>
[Non-text portions of this message have been removed]