On 20-02-2021 02:01, Eric Himmer wrote:
> It was my understanding that the specific embedded version went away
> with v3 (no more fbembed.dll). I used the embedded version with our
> older app which uses FB2. This new version uses FB3 and so I basically
> guessed at using SuperClassic and runs as a service. No idea if that
> was actually the right choice, maybe SuperServer might be better?. I'll
> re-read the documentation as it was a bit confusing to me at the time.
Firebird Embedded still exists, what changed is that
1) There no longer is a separate binary distribution on Windows, you can
use a normal Firebird installation (or zipkit) as Firebird Embedded by
using the fbclient.dll in its installation directory
2) fbembed.dll no longer exists, Firebird Embedded is now fbclient.dll +
plugins/engine12.dll (and supporting DLLs)
Basically, to get a Firebird Embedded, all you need is to unzip the
zipkit, optionally delete the .exe files, and point you application to
The choice for server mode probably doesn't matter that much for local
single user use, though - if your application makes more than one
connection - SuperServer might have some benefit due to shared cache.
However, my suggestion to try another server mode was primarily intended
as troubleshooting/potential workaround: maybe the problem you have
doesn't occur with one of the other server modes.