Mike,

>>I strongly suggest nevere to use these features *unless* there is no other way out.

>I suppose its all preference, because I like them. I don't want to argue or anything, just to let you know there is a supporter of these methods.

I don't think it's preference.. I believe this feature is not neccesary in 99% of the cases where it's used now. On top of that I believe that in the vast majority of cases it proves a bad design. In other cases where it may be usefull it may prove shortcommings of the VFP language (missing events).

I believe that experienced developers would be very carefull when using this feature. Less experienced developers might use this feature way to easy (VFP gives this possibility, so why not use it..), and eventually resulting in less maintainable, constructive code.

I truly believe that if something has no real added value to the language, don't use it. VFP already has lot's of commands and functions and other functionality... don't make it any worse for VFP newbies to write good VFP code.

Maybe you can describe a well defined case where it is usefull and can't be accomplished in another easy way. Maybe you can convince me i'm wrong...


Walter,