Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Return .f. still allows exit from field. Why?
Message
From
28/08/1999 17:35:20
 
 
To
27/08/1999 21:17:05
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00258304
Message ID:
00258868
Views:
10
Sorry Jim
[SET Densemode=ON]

but I haven't a clue what you're trying to tell me!

>Harry,
>
>You do NOT have a return statement for the second nested messagebox sequence, so the default of .T. will be used.

by the "second nested messagebox sequence" I take it you mean the one asking "Are you likely to enter further Payments"
which does indeed not have a return statement. But why should it need one? Or, even if it does, how is its absence affecting the behaviour of the first return statement (which correctly kicks in when the user says 'No') and how does it exhibit this selectivity only when running the code from a subclass and not when running as first level code in a textbox valid?

Is this some quirk I don't understand about subclassing or am I missing the point altogether?

me confused

Harry

>
>>here is the precise code:
>>
>>if not IgnorePaymentTomorrow
>> if this.value=date()+1
>> action=messagebox("You have entered Tomorrow's date - "+dtoc(thisform.paydate)+chr(13);
>> +'Is this what you really meant?',259,'Payment Tomorrow!')
>> if action<>6
>> return .f.
>> endif
>>
>> action=messagebox("Are you likely to enter further Payments (during this session) with Tomorrow's date?",259,'More Tomorrows?')
>>
>> if action=6
>> ignorePaymentTomorrow=.t. && don't irritate the user if they've already told us they're entering more like this
>> endif
>> endif
>>endif
>>
>>
>>the debugger shows that answering No correctly make 'action' =7 and the code runs the 'return .f.' line and exits the valid but moves directly to the lostfocus rather than back to the setfocus.
>>
>>any ideas?
>>
>>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform