Hello,
yes .. it looks a bit akward .. it's not a ideal solution but rather a workaround ...
cant't answer your questions .. i've not designed it like this ..
but i don't see any problem with this approach .. you also gain a bit more flexibility since you can return arrays, more than one value etc ..
i use this class as my parameter object
DEFINE CLASS oParameters AS Relation
FUNCTION THIS_Access(lcProperty)
IF !PEMSTATUS(THIS,lcProperty,5)
THIS.AddProperty(lcProperty)
ENDIF
RETURN THIS
ENDFUNC
ENDDEFINE
so i don't have to add properties at designtime ..
in certain cases it also helps to keep interfaces clean .., just pass a parameter object and you never have to change the interface, but keep the flexibility of adding as much properties/parameters as you need later on ..
Regards
Christian