Jason,

> 1. We're using the latest OpenSource Interbase (6.0.1.6 Open
> Edition)... Moving to Firebird is definitely an option in the
> future, however for right now, we're trying to fix the bugs we have
> (The devil we know, versus the devil we don't, and all that..
> Possibly in the new IBX rewrite of our software).

Although I may be a _little_ biased, I think it is safe to say that
Firebird is far ahead of IB OE. Firebird has at least 25 fixes to bug
which 'plague' IB 6.0 (both OE and certified).

Also, Borland committment to the OpenSource product is less than clear,
they have changed their committment with the release of 6.5.
Originally, they had committed to keep the OE updated with all core
engine changes, now it all bug fixes -- they also have a 'unique' view
of bug fix vs. new feature.

I think that you should be reviewing your options now, rather than
later.

<snip>

> Solution 1 is something we'll be discussing. However, our concern is
> when Interbase and Firebird diverge enough that components to access
> one won't work to access the other (Specifically Interbase Express).
> If there are going to be IBX components to do the same job, with at
> least the same performace, then we're fine.

Jeff Overcash has already stated that IBX and IBConsole will not support
any Firebird custom features -- so unless you plan to be with IB forever
(the 'certified' version since OE life span is unknown), you should
evaluate your options.

Fortunately, if you make a wise decision now, you won't be affected by
the any divergance which might occur. Both IBOjects and FIB (the step
father to IBX) both have good support for Firebird and Interbase and
likely to maintain support for both products.


--
Sean Leyne

There is nothing wrong with Interbase,
that can't be fixed with Firebird.
http://FirebirdSQL.org