|Subject||Re: [firebird-support] Tools for stand-alone databases|
> >2. Support for stand-alone databases is extremely sparse, or perhapswant
> >I so not know where to look.
> Stand-alone databases? Firebird databases can't "stand alone", if you
> to access them at all. There is a server to manage databases and a clienta
> to access the server by way of requests.
> Are you asking about the Windows "embedded server" model? Where you load
> DLL from your application, that contains both the client and a serverstructure
> instance? If yes, then it's not more or less sparsely documented than
> anything else. The embedded server is the Superserver, without user
> authentication or the ability to be accessed remotely. Directory
> matters and is documented in the Firebird 1.5 release notes.I would like to make a comment to this --
> >3. Is there any way to get some of the tools out there to work with
> >stand-alone databases? I have downloaded a few, but they all seem to
> >demand that I am running a Firebird server.
> If you have fbembed.dll in the same directory as the tool - appropriately
> renamed, if the tool requires it - then your tool connects to a server as
> soon as it loads this DLL. If there's a "Server" field in the tool's
> connection dialog, leave it blank. All you need is the absolute path to
> the database file.
Instead of using "Embedded" from your tool, I suggest you install the
Firebird server and use it instead. Only use Embedded for testing your
deployment and the actual deployment.
Well, because when using Embedded, only a single process can access
your datafile -- in this case, your development tool. However, if you
also want - for example - Delphi to use your database, or test your
application while being connected with your Firebird database development
tool, you cannot without logging out in your other tools... Using the
full server is much easier.
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Database development questions? Check the forum!