>>In VFP 8, unlike VFP 7, property values are checked whenever the form is opened in development mode.
>>So if I have a form with
>>Caption =m.cTitle
>>where the expression exists only at run-time you get a non-critical error loading the form in design mode. "Data type is invalid for this property".
>>Worst of all it doesn't tell you which object has the problem.
>>
>>Is there anyway to turn this "feature" off??
>
>If this code is part of a form base class, you can rely on the existance of an application property. Basically, at run time, it will exist. So, you will allow the execution of this line. Otherwise, you just skip that line.
>
>If this code is only present on one or a few forms only, then, you may revise this approach on how it could be made generic and then refer to the paragraph above.

We have hundreds of forms which came from FPW2.6 and work fine now under VFP7. The converter uses the assign statement on just about every property. So I have a thousand or so object properties to fix.

VFP 7 simply returns a blank for any expression which it can't evaluate at design time and it correctly evaluate those it can. If I were to re-code it all for VFP 8 I could probably use the new EVL() function. I was hoping for an environment switch or some other setting which returns to VFP7 behaviour.