--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> At 08:14 PM 16/04/2004 +0000, you wrote:
>
>
> >*** IBPP::Exception inside Database::Connect ***
> >
> >IBPP Message : isc_attach_database failed
> >
> >SQL Message : -904
> >Unsuccessful execution caused by an unavailable resource..
> >
> >Engine Code : 335544375
> >Engine Message :
> >unavailable database
> >
> > ----------
> >
> >What am I doing wrong?
> >
> >I've changed nothing else in the code that works
> >for a client-server relationship.
> You won't be able to connect to the database if something else is
> attached to it., e.g. a dbadmin tool, an IDE, isql, whatever. That
> makes it an unavailable resource because you client can't get an
> exclusive lock on it.

Thanks Helen:

I'm as certain as a clueless person can be that nothing else is
accessing the ".FDB" file. I've checked the control panel and the
Firebird window has a big red "X" through the icon. I haven't
intentionally started any utilities. I used the interactive SQL
and security utilities, but that was many reboots ago.

> btw, forget what Carlos said about "fb_util.dll". I'm certain it
> was a typo. There is no "fb_util" and nothing (in Firebird anyway)
> tries to load a library of that name. ib_util.dll needs to be in
> the /bin directory beneath your application root if you are going
> to invoke any external functions that need it...it's just a memory
> allocation function--- but perhaps it's dynamically loaded by IBPP
> (only conjecture).

My database needs are simple right now. Until I'm a more capable
user of Firebird and SQL, only fbenbed.dll, firebird.msg, and
firebird.conf are moving from the embedded distribution's directory
to my executable directory, unless one of you folks recommends it.
I'm going for minimum complications now. I also want to keep my
distributed package as small as I can.

I've noticed that every copy of firebird.conf on my drive has
every statement commented out.

> Assuming your embedded server is located in the same directory as
> the application executable, have you tried renaming it to gds32.dll?

Yes. Same problem.

> You see, if your application can't find the database, one has to
> wonder whether it is actually even *loading* the embedded server.
> If you have a copy of fbclient.dll or gds32.dll in the system path
> (e.g. in the system32 directory) it's well possible that your
> application is finding it instead, and looking for a running server
> to connect to.

Like any good Unix bigot, one of my favorite things to hate
about Windows is the need to have every ".DLL" file in every
executable's directory that uses it. You don't have to link, you
just have to track down 20 copies of the dll every time you have an
update. That problem is understood and all non-system dlls are in
the executable directory.

The copy of fbclient.dll in the debug directory is 1.481 KB.
Fbclient.dll for the client/server is 349 KB.

Once again, I appreciate your attention.

Thanks
Larry