Hi Mark,

Every property that starts with = is evaluated when the first form based on this class is loaded. Changing a property in code that is used in one of these expression doesn't have any effect, nor would this expression be evaluated if you open a second form that bases on the same class. If the expression depends on anything that you don't define at designtime, you have to set the value in code, for example in the Load or Init event.

You can test this behavior, if you create an expression that has visual appareance, for example a call to MESSAGEBOX(). Whenever the messagebox pops up, the expression is evaluated.

Christof


>I have a base form where in properties window I set a value for a custom property:
>=IIF(!ThisForm.plTest, '123','456') for ThisForm.pcTest1.
>The default value for ThisForm.plTest = .F.
>In concrete form I set ThisForm.plTest = .T. but at run time ThisForm.pcTest1 = '123'. What helps is if I at design time open concrete form and click on =IIF(!ThisForm.plTest,'123','456')expression line (gets bold). Is there any way to have VFP evaluate values properly without these design machinations?
>Thanks Mark