HI Doug.

I have been burnt in the past by OEM Compoinents and as a matter of policy
dont use them.

Here are the Problems.

Supplier ceases business (TurboPower)
Have to purchase new version with every release of Delphi (7 Times)
Often are not backward compatible.
Code is often poor quality
Poor integration with Delphi.
Heavy commitment to learning new components.
No possibility of porting to C#.NET

In general, OEM components are over priced because of the upgrade policies.

Also, correct me if I am wrong, but with IB Objects I have to commit to the
Data Aware components. ie Delphi DA Components no longer work.

Yes, Borland have made that statement and it pisses me off. That among many
other reasons is why I am moving away from Borland in general.

I am not aware of FIBPlus.

I will go look it up.

Basically I was looking for a straight Port of existing code to FB. I dont
mind changing my SQL because thats externalised from my Apps anyway, but I
draw the line at having to re-engineer my Application Servers from top to
bottom.

Thanks anyway,

Tony.


-----Original Message-----
From: Doug Chamberlin [mailto:yahoogroups@...]
Sent: Friday, July 25, 2003 11:35 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Newbie Qustion


At 7/25/2003 12:36 AM (Friday), Tony Blomfield wrote:

>Also, I am pretty much against using 3rd party components for a variety of
>reasons.

Well, if your are switching to Firebird you MUST use third-party components
because the Firebird project does not provide any Delphi components.
Borland-provided components ARE third-party components in this situation.
Why you would use them when they have stated that they will NOT maintain
Firebird compatibility? The other choices (IB Objects or FIBPlus) are much
better solutions once you get beyond Firebird 1.0.





To unsubscribe from this group, send an email to:
firebird-support-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/