Hi Yuri,

Believe me, we think long and hard about changing existing behavior. That being said, if the "=" issue irks enough people, then maybe a case can be made for a behavior change. I (and others) will continue to monitor this and other sites and take whatever action best supports our customers.


>Many thanks for responses and ideas.
>
>So it is by design. Good to know it. However I would prefer to have known functionality unchaged in the new versions. I cannot see the situation when 'old' functionality like we discuss would cause the problem. In this case why not to introduce another and additional 'label2' class?
>
>
>>Hi Yuri,
>>
>>VFP 8.0 allows captions to be evaluated as string expressions, therefore, a "=" raises an error as VFP expects an expression to follow. You need some other character to come first.
>>
>>>Working on the problem Thread #800841 I have discovered that VFP8 does not accept caption = or chr(61) (='=' or =chr(61)) for regular label. Did anybody meet this situation?
>>>
>>>It is a common label for VFP6 and VFP7. VFP8 accepts only (=' =') with the space before second =.