At 12:39 AM 24/06/2004 +0000, you wrote:

> > >I've followed every single instruction concerning the deployment
>of an
> > >embedded application.
> >
> > Except one: you can't connect to an embedded server using a
>network method
> > (in your case, TCP/IP local loopback): you MUST use local
>connect. Remove
> > localhost: from the connection string and it will work - as long as
>you are
> > not trying to access a database file that's located on a share or
>mapped
> > drive, of course...
> >
> > /heLen
>
>The README_embedded.txt file that comes with the .zip of the Win32
>embedded package says this:
>
>" 2.2. Database access
>
> The embedded server can act as a true local server
> accessing databases on a local machine, and as a remote
> gateway which redirects all network calls to another
> hosts (i.e. works as a client library). Note that you
> cannot connect to the local standalone Firebird server
> using the local connection string (without a host name).
> It applies to IPC connections only, because they use
> the same format of the connection string; but you can
> connect to the local standalone server via TCP/IP localhost
> loopback or via the named pipes protocol.
>"
>
>I understood the above as specifically stating that "I can connect to
>the local standalone server (the embedded?) via TCP/IP localhost
>loopback or via the named pipes protocol".

I'm not surprised: it's quite a confusing piece of doc. The "local
standalone server" means the full server. What it's saying in effect is
that you can use fbembedded.dll as a regular client to a local server as
long as you don't use the IPC local string (because fbembed.dll needs to
reserve this for the embedded connection).

The release notes (written by me) aren't helpful with regard to the
connection string for embedded, either. I'll see to it that both docs get
fixed.

/heLen