> I had some significant issues if I used FB to access an IB database
> file. It was imperative to backup the IB database and restore it as FB
> database. This might or might not be an issue for you if you distribute
> a prepared database file (with all tables, procedures, triggers etc.
> created); if you instead create the database file from scratch, then you
> should be OK.
>
> Also, some statements behave differently under IB and FB (e.g. raise an
> error in one and work normally in the other - some CASTs, I think, and
> perhaps AS used in certain situations).
>
> *******************
> What's happening in our case is the converse ... our app uses two .FDB files created in Firebird. The app and the files are copied to the appropriate directories on installation, along with a .INI file to point to the .FDB file location. Our user had copied this down onto a workstation that had IB6.5 as its server engine. Apparently, our Delphi app, using IBObjects TIBODatabase components, was using the IB server to connect, read & write to the .FDB files. So it's not the .FDB files I need to check, it would be something to do with detecting what server engine is running. Any hints?

Once connected (if a connection succeeds at all in your mixed
environment), check out the various properties of:

TIBODatabase.Characteristics


Btw, if we are talking about a single desktop deployment, you might
consider including/using Firebird Embedded in your scenario.



--
With regards,
Thomas Steinmaurer (^TS^)
Firebird Technology Evangelist

http://www.upscene.com/

Do you care about the future of Firebird? Join the Firebird Foundation:
http://www.firebirdsql.org/en/firebird-foundation/