Nadya,

I guess it would be considered a bug, I don't know. But, if your form has controls in containers, be aware that SetAll will not affect them anyway. At least I don't think it would. You can take the method I gave you and move it out of an assign method and into a new custom method that takes a container object as a parameter and recurse it down to all levels if necessary:

PROCEDURE TurnOffSOE(toContainer AS Object)
	LOCAL loObj AS Object

	IF VARTYPE(toContainer) # 'O' OR !PEMSTATUS(toContainer, 'Objects', 5)
		RETURN
	ENDIF

	FOR EACH loObj IN toContainer.Objects
		IF PEMSTATUS(loObj, 'Objects', 5)
			this.TurnOffSOE(loObj)
		ENDIF

		IF PEMSTATUS(loObj, 'SelectOnEntry', 5) AND loObj.SelectOnEntry
			loObj.SelectOnEntry = .f.
			loObj.Left = loObj.Left
		ENDIF
	ENDFOR
ENDPROC

HTH,
Chad


>Interesting! Do you think it's a bug? Why setting the property in run-time doesn't have an effect?
>
>This particular form has lots of objects with inner containers. I guess, I need to find a better way to achieve my goal.
>
>Thanks again.