|Subject||Re: [IBO] tib_ vs. tibo|
> We have decided to convert to ibobjects in stages and not all atAFAIK there is little speed difference. The TIBO components use TIB_*
> once (since our application is too large and complicated). Assuming
> ibo can coexist with bde, is it better to go with the tib_
> components or the tibo components? I know that some 3d party
> components (which we use) would only work with the tibo components.
> Are the native components faster then the tibo ones? Thanks.
components internally, so there is an extra layer of code involved but
I think the overhead imposed by this is minimal.
You can mix and match to a certain extent. For example using native
components for your forms and controls, while using TIBO components to
support your report components. Or if you prefer use the TIBO
components for all your interface work (if you are tied to TDataset
stuff for the interface) but use TIB_Cursor and TIB_DSQL for
manipulations in code (import/export, batch processing etc).
The native (TIB_*) components have several advantages - such as search
mode and the various native controls (TIB_Edit etc). (Not to mention
the ability to use my Enhanced Components ;-) They also tend to be
more configurable to get the best out of your client/server
application, because that is what they were designed to do.
It takes some time to learn all the features and capabilities on the
native components. While many aspects are much the same as the
TDatase stuff, there are many more options and much greater control.
This can be confusing at first but it is worth it (IMO).
So my *opinion* is that if you have the choice then proceed with the
native (TIB_*) components whereever possible.
Geoff Worboys - TeamIBO