> Alan, actually he can use fbembed.dll for all his access and just change a

setting

> on app to access a remote database.

I think point of Alan's post was that you'd detect the *setting* that causes
it to run embedded vs. remote, rather than trying to use some other kind of
heuristics. It depends on which library you use to access Firbird, but for
example, in the .net provider you select whether you want embedded or client
via the ServerType connection string parameter. So your app just needs to
look at the connection string to work out whether it's going to be embedded
or remote.



Dean.



[Non-text portions of this message have been removed]