| Subject | RE: [IBO] overriding SQLName property / handling keywords |
|---|---|
| Author | Brian K. Woods |
| Post date | 2003-02-07T16:12:06Z |
Marco,
past.
With "other" databases and their respective development components,
I have often cursed my habit of using such prefixes, but I have always
decided that
a little extra work is worth guaranteed avoidance of future reserved
name conflicts when upgrading versions or even porting to a new db.
However, (and this is a MAJOR kudo for Jason and IBO), since moving into
Firebird and choosing IBO,
this "con" as you so gently called it, is minimized. Just leverage IBO's
capability
to set the fields' display names in one place ( the connection object's
FieldsDisplayLabel property ).
Sure, you have to set them up once, but, as you point out, you'd have to
review and change many
of them anyway for end-user readability.
BTW - If you aren't using this ability of IBO, you are spending a lot of
extra time setting up various aspects of
your query fields anyway! ;-)
Cheers,
Brian
> -----Original Message-----Yes - that is an unfortunte side-effect I have dealt with myself in the
> From: Marco Menardi <mmenaz@...> [mailto:mmenaz@...]
> Sent: Thursday, February 06, 2003 7:24 PM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] overriding SQLName property / handling keywords
>
>
> I don't use notation for table name prefix, so my field name often are
> already ok as display labels (in grids of IB_Edit with autolabel).
> This way I save a lot of time (of course, sometime their name is too
> cryptic, so I have to define a display name).
> In your example I imediatly have (undersocre is automatically removed
> by IBO):
> ID
> NAME FIRST
> NAME LAST
>
> Just to point out "the cons" ;)
> regards
> Marco Menardi
past.
With "other" databases and their respective development components,
I have often cursed my habit of using such prefixes, but I have always
decided that
a little extra work is worth guaranteed avoidance of future reserved
name conflicts when upgrading versions or even porting to a new db.
However, (and this is a MAJOR kudo for Jason and IBO), since moving into
Firebird and choosing IBO,
this "con" as you so gently called it, is minimized. Just leverage IBO's
capability
to set the fields' display names in one place ( the connection object's
FieldsDisplayLabel property ).
Sure, you have to set them up once, but, as you point out, you'd have to
review and change many
of them anyway for end-user readability.
BTW - If you aren't using this ability of IBO, you are spending a lot of
extra time setting up various aspects of
your query fields anyway! ;-)
Cheers,
Brian