Subject | Re: Backing up when Embeded Server Used? |
---|---|
Author | inoffensive_2009 |
Post date | 2008-11-18T06:00:44Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
work with an embedded server. In some Delphi/IBX versions this does
cause a problem in the IDE, because IBX hard-wires an
InterBase-friendly version string into its validity testing and it
will baulk if it doesn't find one in the library properties (the
problem that is solved for the client-only client library by
generating the IB-friendly version specifically with instclient.exe).
For testing the deployment mode, close any connections that are open
in the IDE and in the IDE's Run mode; then move the latest copy of
the executable into your test application setup each time for running
outside of the IDE.
executables belonging to the server version of the deployed
fbembed.dll need to be in the application directory of the embedded
setup. Service Manager calls DO NOT need the equivalent CLI
executables, however...SM invokes the identical code in modules within
the fbembed.dll itself.
Thanks Helen:
It's late in the development of this product, and I think I'll
continue to use the embedded server for this product's development,
unless presented with compelling evidence to do otherwise.
As you can see, the service manager API is all new to me, I thought
I'd need to use the command line for tasks that are covered in the
API. I'll continue to learn how to use that.
As always, I appreciate everybody's effort to help me.
Thanks
Larry
>would have to be renamed to gds32.dll. A client-only client won't
> At 09:02 AM 18/11/2008, Adam wrote:
>
> >> I see references to something called gds32.dll in the Interbase
> >> documentation. But I don't see that it's ever been brought into my
> >> system with downloads of either the server or embedded Firebird.
> >>
> >> What am I missing?
> >
> >The README_embedded.txt in the embedded docs?
>
> At 09:02 AM 18/11/2008, Adam wrote:
>
>
> >gds32.dll is the client library used by Interbase. At some time in
> >Firebird's history, it was renamed to fbclient.dll. If you are using
> >components designed specifically for Interbase, you will need to
> >either define the name of the client library (if possible), or rename
> >the client library to gds32.dll.
>
> It should probably be pointed out that it is ** fbembed.dll ** that
work with an embedded server. In some Delphi/IBX versions this does
cause a problem in the IDE, because IBX hard-wires an
InterBase-friendly version string into its validity testing and it
will baulk if it doesn't find one in the library properties (the
problem that is solved for the client-only client library by
generating the IB-friendly version specifically with instclient.exe).
>full Superserver and appropriately named client for use by the IDE.
> Don't use embedded as your development client and server. Set up a
For testing the deployment mode, close any connections that are open
in the IDE and in the IDE's Run mode; then move the latest copy of
the executable into your test application setup each time for running
outside of the IDE.
>that invokes any of Firebird's command-line tools, then the CLI
> It's also worth pointing out that, if you plan to deploy anything
executables belonging to the server version of the deployed
fbembed.dll need to be in the application directory of the embedded
setup. Service Manager calls DO NOT need the equivalent CLI
executables, however...SM invokes the identical code in modules within
the fbembed.dll itself.
Thanks Helen:
It's late in the development of this product, and I think I'll
continue to use the embedded server for this product's development,
unless presented with compelling evidence to do otherwise.
As you can see, the service manager API is all new to me, I thought
I'd need to use the command line for tasks that are covered in the
API. I'll continue to learn how to use that.
As always, I appreciate everybody's effort to help me.
Thanks
Larry