dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Visual Basic
Expertise: Intermediate
Aug 21, 1997

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Using LostFocus Events with Command Button Properties

If you're using LostFocus events but would also like to set the Default or Cancel properties for command buttons, you'll run into a confusing situation. Those properties trigger the Click event when the user presses either Enter or Escape without ever transferring focus to the command button. To trigger the "missing" LostFocus, you need to explicitly transfer focus yourself, and then call DoEvents to resequence to a VB chain of events. (Don't be scared by the naysaying over DoEvents--it's extremely useful in this situation and can cause no ill effects!) Use code similar to this:
 Sub Command1_Click () 
Command1.SetFocus 
DoEvents 
If Not (ActiveControl Is Command1) Then 
'Focus was transfered elsewhere 
'by validation code 
Exit Sub 
Else 
'Proceed with Click event code 
End If 
End Sub 
Karl E.
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date