Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Inkey value for X close button on top of right hand corn
Message
From
23/09/1997 11:15:01
 
 
To
23/09/1997 09:15:17
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00051043
Message ID:
00051218
Views:
37
>>>>I have a combo box and its validate code attached to valid method. If a user wants to get out the form by clicking on the top of right hand corner X button. It always return a valid error message first before get out.
>>>>
>>>>I would like to avoid the valid code by checking what inkey code is for X close button (like escape key inkey code is 27). Any suggestions?
>>>>
>>>>Jim S
>>>
>>>That's a good example why it's not healthy practice to use Control.Valid events. IMHO, the right solution is to move all validations to cmdSave.Click event.
>>
>>Ed, this certainly solves the problem of avoiding the Valid clause for certain key-strokes. Unfortunately most of my clients want validation before they leave the field, not for all fields as they try to save the data. Does your scheme allow for this?
>>
>>Confused in California
>>Barbara
>
>Client is always right, so... BTW, it's better to use Interactive/ProgrammaticChange for validation purposes (see this thread case).

I have attempted to deal with this situation in the following way (for textboxes). My textbox class has a custom property called changed. Initial value is .F. In interactive change event of textbox: this.changed = .T., and in mytext.refresh: 'this.changed = .F.'. Then when I absolutely NEED validation before the cursor leaves the field, in the valid event of the box 'if this.changed and !empty(this.value) then ...(rest of validation code)' This allows the user to tab through a previously entered invalid or empty textbox (maybe he wants to fill in something else first, or cancel the entry). without having to come up with a valid value just to leave. The valid code only fires if the user has actually tried to enter or change the value of the field. Of course, this method needs backup validation in the form's save method to prevent invalid values from saving. This is all (IMHO) a messy solution, but nonetheless gives the best of both worlds. Nothing is more annoying than not being able to cancel out of a record change before you enter a valid value for some annoying little control. Any comments/ criticisms/ better suggestions?

Erik
Erik Moore
Clientelligence
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform