skip to content »

extremedivision.ru

Vb net validating close form

-- Terry "Al Reid" wrote: Terry, Yes I've been following it.

vb net validating close form-36

The thing that this approach does not allow (unless I've one again neglected the obvious) is using the escape key to trigger the form cancel. Y Dim HWnd As Int Ptr = Window From Point(p) If HWnd = CType(Me. Handle Then Return True Else Return False End If End Function \\\\\\\\\\\\ -- Al Reid "Al Reid" I had tried all of that, *BUT*, I had neglected to set the button's Causes Validation to False. I reprogrammed the device to only send the CR and now the problem is solved. -- 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 Hi Al, There is another property at the form level that affects how this stuff works - Auto Validate. Close() End Sub Private Sub Text Box1_Validating(By Val sender As Object, By Val e As System. Somewhere in all of that, something must be getting crossed up. For example, I have another application that uses a wedge type barcode reader. Maybe you should be using the Key Down event instead of the Key Press event. here is a line copied from the documentation: "The Key Press event is not raised by noncharacter keys; however, the noncharacter keys do raise the Key Down and Key Up events." My guess is that the gun is sending some noncharacter data to you. The form's Key Preview is set to True so that I can handle key events on the form... If I connect a gun type, the program fails and the cursor jumps to a text box that has it's Tab Stop property set to False. Print in the Form's Keypress event all three methods display the exact same key codes. -- Al Reid "Terry" Hi again Al, On the barcode reader problem. When I click on the cancel button it doesn't even get to the cancel.click event until AFTER it has done the validating. The form's Key Preview is set to True so that I can handle key events on the form... If I connect a gun type, the program fails and the cursor jumps to a text box that has it's Tab Stop property set to False. Print in the Form's Keypress event all three methods display the exact same key codes. -- Al Reid "Terry" Terry, I guess we have a similar background. 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. -- Al Reid "Terry" Hi again Al, On the barcode reader problem. The users have "required" several features such as navigation with the enter key instead of tab and also that all of the text gets selected upon entering a field, etc. 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. 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. Also in the docs on Key Down there is a mention of "Is Input Key" which I will have to look into. I did figure it out though I don't remember having done this yesterday - but I must of - your going to love this - set the text box's causesvalidation to False! Maybe the only thing that should cause validation is the OKButton and then do all the validating - I will let you know what I discover. To Short Date String Else Msg Box("Please enter a valid date.") e. As far as the 'gun', it may be better to write a console app. -- Terry "Al Reid" wrote: 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.

-- Al Reid (who didn't mean to hijack the thread) "Terry" Well it works for me - but one thing I left out - you need to set the cancel buttons 'causes validation' to false. The gun was putting out a LF after the CR and in the Key Down event it showed up as a Keys. Validating If Not mbln Cancel Then Dim dte Date As Date Time If Date Time. I am new to VB comming from VB6, but that was also the case in VB6. I tried to recreate what I did yesterday and ended up having the same problem you are having! Why it would stop on a textbox with tabstop property set to False - I have no idea, unless it is a behavior of the container its in. Maybe you should be using the Key Down event instead of the Key Press event. here is a line copied from the documentation: "The Key Press event is not raised by noncharacter keys; however, the noncharacter keys do raise the Key Down and Key Up events." My guess is that the gun is sending some noncharacter data to you.

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.

When you click on the button the validating event fires. If the handle matched then immediately exit the Validating event without setting e. -- Al Reid Well it works for me - but one thing I left out - you need to set the cancel buttons 'causes validation' to false. 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.

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. -- Terry "Al Reid" wrote: Ok, I remember now, you are using a modal msgbox in your validation code. If you were using an errorprovider, then the error would be set, the focus would be returned to the textbox, the form closing event would then fire and it changes the cancel flag to false and the form closes.

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. Also in the docs on Key Down there is a mention of "Is Input Key" which I will have to look into. -- Terry 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. Maybe you should be using the Key Down event instead of the Key Press event. here is a line copied from the documentation: "The Key Press event is not raised by noncharacter keys; however, the noncharacter keys do raise the Key Down and Key Up events." My guess is that the gun is sending some noncharacter data to you. -- 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.