>>Well, well... this is something I'd never have found by myself, unless I spend hours on it. Well, with my attitude, I also wouldn't stumble upon it, but then... this is something I may use well, if it won't change across versions. Supposing I need a property to be consistently same throughout the application, but different within various applications, I could use an UDF as a property source; it would fire only once. I can imagine good uses for this behavior.
>
>I only found it because of my first attempts at creating a CSet class to manage SET environment states.

The syntax for SET statements is so inconsistent, that my solution is less than half as elegant than what I wanted it to be.

>I've seen one person using it as an attempt to get "static" properties for all objects of a given class. I'm not sure you can count on this "undocumented" behavior exisiting for the rest of VFP's lifetime.

Sure, I guessed (feared) this may be the case. One thing is sure - Init() will fire, else the object won't exist. Everything else "is subject to change without notice"...