Subject | Re: [IBO] Is IBX better than IBO when used threaded ? |
---|---|
Author | Pelle F. S. Liljendal |
Post date | 2003-11-05T18:12:36Z |
The moral must be: Use the correct tool for the job at hand. Even
when you are used to use the "Hammer" and its your favour tool in
the whole toolbox, you migth be better off to use a drill to make
that small hole in the wall <G>.
My "prime directive" for my future use of IBO is: use IBOxxx
components ONLY when I HAVE TO (e.g. when used with "normal"
editors/grids and reporting tools), otherwise use the IB_xxx
components. Beside that (as you suggest) only use a scrollable query
if you need it to be scrollable and write that "optimized SQL"
Pelle
when you are used to use the "Hammer" and its your favour tool in
the whole toolbox, you migth be better off to use a drill to make
that small hole in the wall <G>.
My "prime directive" for my future use of IBO is: use IBOxxx
components ONLY when I HAVE TO (e.g. when used with "normal"
editors/grids and reporting tools), otherwise use the IB_xxx
components. Beside that (as you suggest) only use a scrollable query
if you need it to be scrollable and write that "optimized SQL"
Pelle
> I do keep to the rule:don't
>
> (a) IB_Query (or IBOQuery in your case) is for:
> Selecting data that are shown to the user, eg browsing (but please
> do a SELECT *, just select the fields you think you have to showwithin
> a grid. If you use SELECT * be sure you have only a few records(best:
> one) to show).server
> (b) TIB_Cursor: processing data that have to be selected from the
> but not be shown to the userfor
> (c) TIB_DSQL: Doing INSERT, UPDATE, DELETE statements, even used
> executing non selectable stored procs
>
> Following these rules you'll get a real fast application.
>
> My 2 c.
>
> Luc.