Subject | Re: Unable to use either fbembed.dll nor the class server |
---|---|
Author | Jeff Lynn |
Post date | 2006-05-02T03:36:46Z |
Please don't response to the this thread, which had been solved two
weeks ago and I am now using full API for both stand-alone and remote
server with dynamic sql and building sqlda on the fly. I am flying.
Jason somehow picked up this post and start answering, so please do
wast time on this thread.
jml
weeks ago and I am now using full API for both stand-alone and remote
server with dynamic sql and building sqlda on the fly. I am flying.
Jason somehow picked up this post and start answering, so please do
wast time on this thread.
jml
--- In firebird-support@yahoogroups.com, "Adam" <s3057043@...> wrote:
>
> --- In firebird-support@yahoogroups.com, Jason Dodson <jasond@> wrote:
> >
> > Um, try:
> >
> > CONNECT localhost:D:\APPS\Firebird\examples\employee.fdb;
>
> Well if that works then he is not using the embedded engine. He would
> be using whatever full server is listening to 3050 on the local machine.
>
> If you pass through a TCP connection string, the embedded engine
> behaves like a standard client. This is clearly stated in the readme
> in the embedded install.
>
> Classic is the other way around. You can not (in Windows) connect to a
> classic server using a local connection string, and so you will need
> to put 'hostname:' first. This is also clearly stated in the quick
> start guide amongst other places.
>
> Superserver is able to accept both, except when connecting from a
> terminal services session in which case only the TCP method works.
>
> The best way to handle this is to use an ini file or equivalent to
> build your connection string, and depending on which server type you
> are connecting two, adjust your switch.
>
> Embedded should not be used until you are ready to deploy. It prevents
> multiple processes from connecting the single database, which is a
> real PITA, because now you can't use your admin tool to confirm
> records are successfully added etc.
>
> Classic is not really the one you want to develop against for embedded
> systems. Since embedded server is superserver in a dll, you are far
> better off developing against superserver which will allow you to
> develop using the local connection syntax and simply substitute the
dlls.
>
> Adam
>
>
> >
> >
> > Jeff Lynn wrote:
> > > Help! I am extremely fustratated, not able to use anything after
> > > download.
> > >
> > > First, I tried to use the fbembed.dll from embedded download with a
> > > sample code api1.c from the server folder of the class download. i
> > > can compile and link but unable to create database as suggested in
> api1.c.
> > >
> > > I then switch to startup up the classic server service, and use the
> > > "Quick Start" doc to verify the installation using the ISQL utility,
> > > as suggested in the Quick Start:
> > >
> > > D:\Apps\Firebird\bin>isql
> > > Use CONNECT or CREATE DATABASE to specify a database
> > > SQL> CONNECT 'D:\APPS\Firebird\examples\employee.fdb'
> > > CON> user 'SYSDBA' password 'masterkey';
> > > Statement failed, SQLCODE = -904
> > >
> > > unavailable database
> > > SQL>
> > >
> > > How come?
> > >
> > >>From all the good news from all the posint, I was extremely
unlucky to
> > > get it going. I was being very careful and only download the
release,
> > > not the beta 2.0 version yet I still unable to do anything with the
> > > installation, either server or embedded.,
> > >
> > > jml
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >
> > > Visit http://firebird.sourceforge.net and click the Resources item
> > > on the main (top) menu. Try Knowledgebase and FAQ links !
> > >
> > > Also search the knowledgebases at http://www.ibphoenix.com
> > >
> > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > The information transmitted herewith is sensitive information
> intended only for use to the individual or entity to which it is
> addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon, this information is strictly prohibited. If
> you have received this communication in error, please contact the
> sender and delete the material from your computer.
> >
>