Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Label caption no longer support expressions
Message
From
10/02/2003 03:12:50
 
 
To
09/02/2003 15:12:07
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00751199
Message ID:
00751308
Views:
23
Hi Tore,

Andrew is right, but to make clear his post = put a space before the equal sign in the quotes.

There were some behavior changes for label captions, primarily to allow character expressions where not allowed before.


>Hello all
>
>I first thought that I had discovered a serious bug in VFP8, the RTM version, but after a lot of painful digging I will downgrade it to an undocumented change in the behaviour. Or maybe I have used an undocumented 'feature' for years, and which also worked in the VFP8 beta.
>
>The first thing I did after installing the RTM version, was to 'do' some pretty advanced forms I have designed, and they all worked perfect, with the new look which I really like. (I use Win XP Pro). But when I wanted to modify the forms, VFP8 started to report a lot of error messages, eventually making me crash VFP.
>
>Many places I used expressions in the caption property for labels which obviously is no longer supported. For instance I have a label with this caption property: "='© BEAS-2003 - Versjon '+thisform.versjon ". Another label has a UDF as caption. (The "s are used here, not in the property sheet)
>
>This has been OK for years, also the VFP8 beta, the labels were blank at design time, and populated correctly at runtime. But VFP8 RTM does not like this, and I had to press Ignore many times plus cancel out of the procedure editor even more times, before eventually my form showed up in edit mode. The first times I was sure that I had discovered a bug, and tried to 'cancel' out, which was practically impossible. But after some digging I found the problem which was relatively easy to fix. I put some dummy text in the caption properties and populated them with the wanted values in the init event.
>
>The big issue here is that this behaviour does not seem to be documented. Even worse, you don't get any clear message about what the errors are, and absolutely nothing about where they are. So it can take quite a lot of time to fix.
>
>Does anyone have any comments to this new behaviour? I think Microsoft should post a message about it.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform