>Hi Bob
>
>Replay to
>
>"But, why don't you init the properties in code using your contants."
>
>- VCX properties are evaluated one time only, when class structure is build on memory to create "Class memory image"
>- code in Init is evaluated every instance of class or subclass
>- code in properties are fast visible and simple to try on "Window properties"
>- code in Init require my memory to recall DODEF() or class::init on subclass
>- if I have 5 property with 5 values #define, in the subClass of it I want to change 2, as I make with Init? Inheritance it is fried!
>- etc
>
>"Have you actually submitted this somewhere? I think this is the first I have ever seen it, and I usually keep up with the wish lists."
>
>Strange that nobody had placed this problem before now.
>
>Hello
>Fabio

I think I had asked for that shortly after VFP5 came out. I've since worked around it so often that I've just learned to live without it. (code in the .Init method)