> > Forget embedded server for a multi-user scenario (unless you are
> using it
> > for a server-based application server tier). If you have remote
> users who
> > need to connect to the same database, the embedded model is not
> what you
> > need. The answer to your "subject" is a resounding NO.
>
> Thanks for your great explaination.
> Yeah my application is actually a 4-tier thin-client server model:
>
> Client <==> business-sever <==> data services <==> datastore.
>
> And my application has been using MSSQL as datasotre.
> Since Firebird opens more opportunity and high performance, my data
> service tier is likely to embed Firebird. However, to be embedded, it
> also needs to open a door for other third party applications to
> access the server. Again the ultimate question is
> "acoording to your comment, an embedded Firebird server does NOT
> support remote accessing such as ODBC?"

Once again... If you want remote access (being it ODBC, native,
ADO, Perl or MyOwnProtocolViaTheApi), use the Server edition.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com