>>Possible, but with all the problem list of VFP I prefer to touch something only when it is tightly necessary.
>>Another example is if a BIND exists on LockScreen, that has to happen only when it changes of value
>
>
>Well I program my BINDs and ASSIGNs such way that they check if the value has changed or not. It is part of my 'defensive programming' strategy. Esspecially within those kind of procedures you'll have to be very carefull, because the developper accessing the property might not have a clue that it is calling some additional code. Therefore I'd like to avoid BIND and ASSIGN procedures unless there is no other convenient way out or something has to be totally transparent and hidden deep in a class without any outside dependencies.
>
>Walter,

I Agree here, but this is only a problem of documentation.
Unfortunately, in the systems of development the documentation is still to the
"age of the stone".
In our Framework it is planned a system of multilevel documentation integrated with the system of development, but it is not developed yet.