> > In my App I'm using your old FieldDisplayLabel very often
> > and I want to switch to IB_Label next time.
>
> If you need an independant label then yes, I do suggest you change
> over to IB_Label as I will eventually drop the old TLabelEnh from the
> EnhComponents collection. Since some of the defaults are different in
> IB_Label I have thought that I may create a derivation that implements
> a variation of IB_Label with the same defaults that I had in the old
> TLabelEnh - does this matter to you?
>

What defaults do you mean ?

>
> > The problem I have, is that, when my app starts I'm doing
> > a lot of initializiations before the Queries are prepared
> > and one thing I need, is the DisplayLabel of a field.
> > Please tell me, what you think.
>
> My first question would be:
>
> Why not use AutoLabel? It implements TIB_Label internally, and so has
> all the same features but, as you have seen, is much more dynamic. If
> there is a problem or shortfall in AutoLabel Tobias and I would like
> to know about it.
>

I'm using the Label not only with IBO-Controls, but also with other
controls, so it gives more flexibility.

>
> > Is it possible to implement this feature in your
> > IB_Label-Component ?
>
>
> 2. I could implement the setup so that, when the dataset is not
> prepared, the label will automatically search the associated
> FieldsDisplayLabel properties for a matching label value. As long as
> the names are associated with the field name and not the domain or
> sqltype then this should work.
>

That's exactly, what I'm looking for. It would be great, if could
implement this.