Phil,

  What you call the dll is entirely up to you, but I would think that BloodyAnnoying.dll is probably just asking for trouble.

 

  The demo that I created uses gds32.dll as the name for the firebird server because the demo was built using IBX components, and IBX wants the client library to be called gds32.

 

  If you are using IBO, UIB or FIB components, then you may have the option to specify the dll name but I don’t know how or where you should do that.

 

  If my little demo program worked for you, then you should be able to plop your own database into where I put employee.fb and change the stuff in unit1 to point to that (and change the sql in query1 so that it shows something more sensible).


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Middlemiss
Sent: Friday, 29 April 2005 1:57 p.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] Unavailable Database

 

Thanks for that Trevor, that got rid of the "unavailable database" message now! (which is very good). I think I may have a version issue though, cause I'm getting an error about "Implementation of text subtype 52 not located". I am using Firebird 1.5 and the embed zip that I downloaded said to rename the embed.dll to fbclient.dll (gds32.dll was supposed to be for backward support). So now I'm a bit confused - should it be fbclient.dll or gds32.dll? gds32.dll seems to connect ok, but maybe I'm then using something incompatible in the database? Aren't Fridays fun?!?!

Cheers,
Phil.


_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi

Reply via email to