> Paul,
>
> I've just come into the office and seen this message from Friday. Let
> me look for the magazine; all the names are too similar for me to
> quote off the top of my head. As for the rest (which I am not
> back-quoting): if you are dropping Paradox/BDE in favor of
> Interbase/IBO, then you are essentially rewriting the app altogether.
> In this context, and given your familiarity with client/server, using
> the IB_ access components and the IB_ visual components is probably a
> good idea. The only drawback is finding a reporting tool that will
> work with it. I know ReportBuilder will, but that's pricy.
I have been looking at a variety of ideas, ODBC was one, but then I
have to support animals like PervasiveSQL (Think of Oracle, with
twice the bugs, half the performance, kludged together by a former
Microsoftie, and you will get the right idea), or MS-SQL (Sybase
wiith twice the bugs, half the performance, kludged together by a
Microsoftie). BDE is an 800lb Gorilla, and IBX, well lets not go
there.
IBO, gives the advantage in that the application only has to deal
with a single database technology, even if Interbase has bugs, either
Jason, or we can work around them, with a forum like this, it's not
that hard. Now that Firebird is taking over, to some extent IB
development, we have an open-source database, that I can throw on a
CD with the product, and let the customer deal with it.
Paul
Paul Schmidt,
Tricat Technologies
Email: paul@...
Website: www.tricattechnologies.com