At 08:25 AM 5/01/2005 -0800, you wrote:

>Hello:
>
>I've got a real head scratcher here:
>
>I'm making an application in D7, using IBO to access FB. Its a student
>testing application, stand alone, using FB Embeded for Windows.
>
>I'm developing it on a XP Pro system. My wife, who will be using it,
>runs it on her Toshiba lap top XP Home system just fine. She bought a
>new, cheap computer for the students to use (2.4 Ghz, 256 mb RAM, has XP
>Home installed) and for the life of me I can't get the application to
>run.
>
>I'm using FB Embeded 1.5 as "gds32.dll" for all installations.
>
>I made a CD-RW disk which has the application and database on it with
>the firebird.conf file and expected directory structure. On my system, I
>turned off the Firebird guardian, since I'm running the fully installed
>FB.

Firebird Guardian is meant for use with the "fully installed FB" - not that
it's an issue here.

>The application runs fine from the CD. It runs fine using my wife's
>lap top from this CD, but it doesn't run on the new desktop system.
>
>On the new desktop, I get the usual "Send/Don't Send" error message,
>saying there is a problem with the application. On looking at the
>technical details, it says it was during a load of Kernel32.dll. When I
>look through the hex information, there is something that says
>"gds32.dll is not installed." (Incidentally, for true MSFT paranoids
>amoung us, it had my password and user name for the database--not that
>they are needed in the embedded FB.)
>
>I tried using "fbclient.dll", too, but no luck. It seems to be something
>to do with not recognizing the database, but I can't think of anything
>that would cause this.

It seems to be more in the area of the application not being able to load
the client library. FWIW, this has been aired many times on the IBO list.
There are various ways to make an IBO app find "fbclient.dll" but the easy
solution is to go with the standard IBO assumptions -- copy fbclient.dll
to the system directory and rename it to gds32.dll. (On XP Home, I think
this is c:\windows\system32).

With a new installation of XP Home it's also rather likely that the
Microsoft C and C++ runtimes are missing. Check in the system directory
for the files msvcrt.dll and msvcp60.dll. You'll find copies of these
files in the ..\bin directory of the Firebird root. Note that there's no
absolute guarantee that your particular installation of XP Home will accept
these versions - try it first and, failing that, go to the Microsoft site
and download the appropriate library pack for your edition.

I'd also want to ensure that the application version for the non-embedded
deployment was pointing to the localhost server (TCP/IP local loopback) and
not to the IPServer, as the embedded version does (by design).

./heLen