Hi Walter,

>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...

Do you create reusable classes that might be considered for public domain much? Not that I do, its just I'd rather set my properties via the traditional way of setting properties, not through methods. That way you can mangle props to the way the need to be (ie UPPER(ADDBS(cFileName))), or let the developer know what he's done wrong:

*Proc iInterval_assign
if not an Integer
   error 'iInterval must be an Integer'
   return 0
else
   return m.eNewVal
endif

That makes a good reminder for you, and another reminder for anything else. Also, they work wonderful for WrapperClasses (ie you set a property of oyur container class for a MAPI activeX contained in the container (oMail.Name = NewVal) which in the assign it stuffs it into the child object (this.MapiSession.DefaultProfile = NewVal) Makes life easier for you and anyone else who wants to use it.