Mike, Bob,

I think you're example is one where it may justify your decision to use the access and assign events, which is to hide complexity, although this can be accomplished with methods just as easy. But I agree from an OO perspective this is not a bad solution at all.

My real objections against the ASSIGN and ACCESS events are:
- An average programmer might be temptated to use these features in the wrong way. The first message in this thread may prove this.
- It might be used to fix bad designs, making things only worse.
- IMO 95 % of the things where these features are used, you could use the old fashioned method approach. I agree some things can be done more constructive with these features.
- Error tracking *can* get a real hell if the programmer is not aware that these features are used for certain properties.
- It does not work in Design time nor does it work for certain VFP native properties (like the rowheight property of a grid).

I'm aware that these argument are quite subjective, but I truly believe that people should be very carefull and rethink their decision twice before they implement these features.

You and me will do so, But I wonder about the average programmer.....


Thanks for the examples, It convinced me that they are usefull in at least some cases.

Walter,