Hi Alan,

Thanks for taking the time to reply and forward this information. Very informative. Do you know where I can find information on how to embedded the database engine in my Delphi 7 application? Or what I need to do to deploy Firebird, should I decide not to go down the embedded route? Thank you.

Regards,
Diego

On Tuesday, November 23, 2004, at 03:51PM, Alan McDonald <alan@...> wrote:

>
>> Hi all,
>>
>> I have a couple of questions.
>>
>> 1) Where can I find some information as to how I can embedded the
>> Firebird database engine and make it part of my application? I
>> presume this means it's part of my Windows executable?
>>
>> 2) What files do I need to deploy the database, should I decide
>> not to go the embedded route?
>>
>> BTW I am developing using Delphi 7.
>>
>> Any help would be appreciated. Thank you.
>>
>> Regards,
>> Diego
>>
>
>Last Thursday's post from Nando
>
>T> Under what circumstances should I as a developer consider using FB
>Embedded
>T> rather than FB?
>
>- you only need to access the database from a single, local process at a
>time and you need the best possible performaces. An embedded database
>connection beats any other protocol in terms of throughput.
>
>- you need to develop a client/server application in which the server
>part needs to be smarter than a database server (i.e. should provide
>additional application services) and you don't want/need to turn it
>into a 3-tier system. In that case, embed Firebird into your
>application server and there you go.
>
>- you have a single-user (1-tier) application that needs local
>storage support with the minimum possible impact on the target system.
>There are plenty of solutions for this kind of deployment, but fbembed
>beats them all in flexibility and feature-richness.
>
>- you have a client application in a C/S scenario (the server being
>Firebird) that needs to connect to the server and also needs local
>storage (perhaps as backup for when the C/S link is broken, perhaps as
>an aid for local processing). In that case you use fbembed as both an
>embedded database engine and as a client for an external Firebird
>server.
>
>- should any of the conditions that made one of the above scenarios
>interesting change, you can upgrade to Firebird stand-alone
>seamlessly.
>
>There could be other scenarios, these are the ones I have tried and
>use. If we acknowledge that having a real "embedded server" (as
>opposed to an embedded "engine", which is what fbembed.dll is) is a
>good idea, which I expect to happen somewhere around the 3.0 release,
>there are even more appealing deployment scenarios.
>
>HTH
>--
>Nando Dessena
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>


Cheers,
Diego