Vb net leave validating


Darin *** Sent via Developersdex Yes, closing the form causes 'validating' to take place. I have come to the belief that the problem we are seeing with the escape key is a bug.One, remove the "control Box" from the form, so the user cant close it that way. in the btn Cancel_Click event: Removehandeler Text Box1.validating, Addressof Text Box1_Validating -- Terry "Darin" wrote: I know that, but the problem is when the user clicks EXIT, the textbox.validating event is called BEFORE the cancel.click is done, so the textbox is being validated. According to the documentation: "The cancel button for a form is the button control that is clicked whenever the user presses the ESC key." Which says to me the behavior s/b the same! To Short Date String Else Msg Box("Please enter a valid date.") e.I have a form w/ a textbox and Cancel button on it. When I click on the cancel button it doesn't even get to the cancel.click event until AFTER it has done the validating. As far as the original validation issue, I started a new project (VB2005) and tried your approach It works except that pressing the Esc key still causes the validation event to fire. According to the documentation: "The cancel button for a form is the button control that is clicked whenever the user presses the ESC key." Which says to me the behavior s/b the same! Validating If Not mbln Cancel Then Dim dte Date As Date Time If Date Time. Also note that the "trick" to closing the form is not keeping a seperate "canceling" flag, but to put "e.cancel=False" in the forms closing event.I have a routine to handle textbox.validating, and I have the form setup so the Cancel button is the Cancel button. I am going to start a new thread - calling it a bug and see what happens. Down (Down Arrow) and some how (and I never figured this one out) the next control in the tab order, regardless of the Tab Stop property, got focus. Causes Validation = False Public Class Form1 Private mbln Cancel As Boolean Private Sub Text Box1_Validating(By Val sender As Object, By Val e As System. -- Terry "Al Reid" wrote: Terry, I tried the same scenario in VB6 and found that it works the way one would expect AND there is no need for the m Cancel flag either.As a follow up to my previous post about enhancing the validation controls within Windows Forms, there might be times when you would like to manually invoke the “Validating” event of a control.For example, you might want to have a routine that fires on the form's “Closing” event or a data save method to loop through all the controls on your form and validate them independently to ensure that all controls are valid.I searched google for some ideas and I came across the following snippet of code So, at my wits end, the only concievable way I could think of getting around this problem was knowing when the close event was coming up in the near future and then...*BAM! 'x', and the form closed (insert best Arny voice) IMMEDIATELY. We use a plug-in architecture to load User Controls at runtime. Cancel in the Validating event of a plug-in prevented the host Form from shutting down properly.Adding your code to the User Control solved the problem. It saved me a lot of time after I encountered this problem.



Close() End Sub Private Sub Text Box1_Validating(By Val sender As Object, By Val e As System. The code to tell if the cancel button has been clicked is: /////// Public Declare Function Window From Point Lib "user32" (By Val p As POINTAPI) As Int Ptr Public Structure POINTAPI Dim X As Integer Dim Y As Integer End Structure Private Function Cancel Button Clicked() As Boolean Dim p As New POINTAPI p. As far as the original validation issue, I started a new project (VB2005) and tried your approach It works except that pressing the Esc key still causes the validation event to fire. -- Terry "Al Reid" wrote: Well, I finally solved the barcode scanner problem. Cancel = True End If End If End Sub Private Sub Button1_Click(By Val sender As System. I just don't know what key code combination could direct focus to a text box control that should never receive focus since the Tab Stop property is false and there is no other code that sets focus to the textbox. Also in the docs on Key Down there is a mention of "Is Input Key" which I will have to look into. -- Terry Terry, I tried the same scenario in VB6 and found that it works the way one would expect AND there is no need for the m Cancel flag either. -- Al Reid "Terry" Hi Al, Nearly 40 years for me since my first college FORTRAN IV class! Well, one of the keys you would not see in either the keypress or keydown events is the tab key, which of course will move the focus.You might even loop through all the controls on your form and focus each of them individually (or an individual control by giving it focus then changing the focus to another control), achieving the same effect: Which solution is better?I'd recommend staying away from reflecting on the internal methods and properties of Framework classes.The code I chose to implement the above scenario involved the Validating & Validated events: However, all I wanted to do was exit the form in the first place and not spend the extra cycles querying the database or making things happen on the form before closing.

What was making it tough was the validating event was firing before any other event. *giggle* So I jigged up the following code: I tossed the above code at the beggining of my Validating event, typed a couple letters in the box, click the infamous (more famous than famous) Mr.

One, remove the "control Box" from the form, so the user cant close it that way. in the btn Cancel_Click event: Removehandeler Text Box1.validating, Addressof Text Box1_Validating -- Terry That doesn't work either, at least not for VB2005. Then in the btn Cancel_click event, either set a module level variable like m Canceling to True and then in the validating event ... I've been fighting the same problem for some time now. I think that the only way to do this is to grab the mouse coordinates in the validating event, do a Window From Point API call, then compare the returned HWND to the Cancel Button's Handle. I also got the Window From Point approach working as well. The following code works as you might hope: Public Class Form1 Private m Canceling As Boolean = False Private Sub Button1_Click(By Val sender As System. Private Sub Text Box1_Validating(By Val sender As Object, By Val e As System. As far as the 'gun', it may be better to write a console app. -- Terry "Al Reid" wrote: Terry, I don't do anything with the barcode data in the Key Press event. I guess I could inspect the data in the Key Down event to see if there is a difference. news:78**********************************@microsof .. I am new to VB comming from VB6, but that was also the case in VB6. I added the code to handle the esc key per the "bug" thread and it works.