Hi Alan,

This is what we understand to be the case... and we're doing that now
(in beta :-) ) with no problems.

So, for a single computer install, we just deploy fbembed.dll (and
associated files)... on a 'server' machine, we do a full fb server
install, with the real client.

Regards,

Peter Lee

Alan McDonald wrote:

>The Release Notes (page 52) states of the embedded server:
>
>Database access[:] Only “true local” access is allowed. The embedded server
>has no support for remote protocols, so even access via "localhost" won't
>work.
>
>Helen Borrie on Nov 18 states:
>There are more possibilities in the mix. From the same machine, a user
>could be working with a local database using the embedded server and,
>simultaneously, connecting from the same application (and client library)
>to a database on a remote server.
>
>I'm a little confused now. Are the release notes in error?
>I've tried renaming the fbembed.dll to gds32.dll into the application
>directory of one of my apps and it appears to connect no problem with a
>remote database server.
>
>Can I therefore distribute fbembed.dll (renamed to gds32.dll or
>fbclient.dll - whichever I need) all the time - i.e. forget about the client
>only lib (if distro size is not important)?
>thanks
>Alan
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>
>

--
Peter Lee Mobile: +61 412 011 174 ptle@...
-----------------------------------------------------------------------
Rising Software Australia Pty. Ltd. http://www.risingsoftware.com/
Publishers of 'Auralia' - Ear Training and 'Musition' - Theory Training
Ph: +61 3 9894 4788 FAX: +61 3 9894 3362 USA Freecall: 1 888 667 7839