>Hi Cetin
>
>>What do you mean "OOP wants me to populate the properties instead of passing parameters and I agree with it"? I wouldn't agree, I think but probably I didn't understand.
>
>Yes, you have guessed right. As for OOP I am under the impression that the LPARAMETERS in the init() of a class is something that should be avoided and instead properties are used which are populated in code to replace LPARAMETERS
>
>>oForm = doform()
>>oForm.SomeProperty = somevalue
>
>DoForm() does not do much
>

...
>			loObject = CREATEOBJECT(tcClassName, @tuParm1, @tuParm2, @tuParm3, @tuParm4)
>	ENDCASE
>
>	IF TYPE("loObject.Name") == "C"
>*  ===>  this is where the properties should be populated if I avoid the above call parameters
>		loObject.SHOW()
>
>		IF TYPE("loObject.uRetVal") # "U"
>			RETURN loObject.uRetVal
>		ENDIF
>
>	ENDIF
>...

>
>Probably this was a wrong question and I just got carried away with it. As I will have to manually call .SHOW() in case even if I do something as what you have hinted.
>
>Thanks.

"As for OOP I am under the impression that the LPARAMETERS in the init() of a class is something that should be avoided"
Your impression was wrong IMHO. If you wouldn't feel well anyway then you can do that exactly as I show before the .Show() call. ie:

	IF TYPE("loObject.Name") == "C"
*  ===>  this is where the properties should be populated if I avoid the above call parameters
                    loObject.SomeProperty = someValue
		loObject.SHOW()

Cetin