i have a form hold some textboxes ,writed validating-event code and sometime set cancel=true in validatingnow,the problem is,when i click the close button of the form,the validating-event fired,and the form can't close when the validating set cancel=true,but this not i want.i think click "close" that meaning abandon all the form's data,so it not need validate.how can i do ?
View 2 RepliesI am writing below code for validating compulsary field account no. in form.User's requirement is set focus back on field when error comes :
If txtAccountNo = "" Then
MessageBox.Show("Account no filed can't be left empty")
txtAccountNo.SetFocus
Exit Sub
End If
It's working properly. But suppose user don't want to fill form and exiting from application.Message box keep on appearing till user enters account no.
We have a window that has a text box on it that the user must enter in valid data before going on. So we have put in a message box letting the user know that they have to enter in the correct data before going on in the Leave event. That works just fine, but when the user press ALT+F4, or presses the X in the upper right corner of the window it still goes through the event. We would not like for that to happen. When we were using VB6 the same code was in the lost focus, and when the user pressed ALT+F4, and the X the LostFocus event did not fire, or acted like it did not fire. We have also tried moving the code to the Validating event, but it behaives similar to the Leave event? how to close a window, and either have the Leave, LostFocus, and Validating events not fire when the user Presses ALT+F4, or the X
View 6 RepliesCan we disable the close button on a form ? I can remove the minimize/maximize, but cant find anyway to disable the close button.
View 11 RepliesI am attempting to disable the close button "X" in the controlbox of a form and keep the maximize and minimize buttons. There does not appear to be a way to accomplish this with conventional VB code or using the Form's Properties.
So I ventured into the realm of API's.
I declared the following API Calls and Constants:
Declare Function GetSystemMenu Lib "user32" Alias "GetSystemMenu" _
(ByVal hwnd As Long, ByVal bRevert As Long) As Long
Declare Function EnableMenuItem Lib "user32" Alias "EnableMenuItem" _
[Code].....
I have a form that the user must enter some important information and the only way of leaving of that form is to enter the correct info. By mistake I close that form from the X on the upper right side realizing that my code restrictions on that form was not enough. How can I disable close (X) of that form? I checked the form properties but I couldn't find anything about that just to disable maximize and minimize.
View 7 RepliesIs there a possible way in VB.NET to disable the close button of the main form as I've seen in many installer! I don't want to hide it, I want to completely disable it!
View 3 RepliesI am facing one issue in my VB.net application. In my application I want to disable the close button in all my windows. I am doing this by following code. But the real issue is while I am minimized and maximized the window the close button is getting enabled to the end user. How to permanently disable the Close window.
Public Class CloseButton
Private Declare Function
GetSystemMenu Lib "user32" (ByVal hwnd As Integer, ByVal revert As
Integer) As Integer
[Code].....
Ive been searching around Google and while I have found some answers, Im not sure how to implant them correctly.
I wish to disable the Close (X) button on a Windows Form. I read about ControlBox (I think that the property) but I perfer to do it another way.
Is it possible to disable a form from moving still allowing the user close it? How?
View 10 RepliesI have a VB.NET application writtene using VS 2008 and have been receiving a weird error when a form is closed - it gives me the following error message:
Windows has triggered a breakpoint in MyApplication.exe.
This may be due to a corruption of the heap, which indicates a bug in MyApplication.exe or any of the DLLs it has loaded. This may also be due to the user pressing F12 while MyApplication.exe has focus. The output window may have more diagnostic information.
The immediate window then has this error message:
Critical error detected c0000374
I tried fixing this by just hiding the window, but this simply moves the error up the chain and I get an error when exiting the program as it tries to close the form:
Unhandled exception at 0x7700e29b in MyApplication.exe: 0xC0000005: Access violation writing location 0x00000000.
I don't think I'm doing anything particularly strange in my application - reading from and writing to a database is about as complicated as anything gets for me. I've tried using AppVerifier, but then the program won't even open. I'm at a real loss as I don't know anything about memory management, or what a heap is. I just can't work out why this error is happening
By the way, the application compiles and runs fine on my old 32-bit computer running WinXP professional, but my new 64-bit Windows 7 computer is just not having it, even though I have targeted the compile for x86 and followed every bit of advice I could find on geting it to work in Windows 7. Should Windows 7 and VS 2008 really be incompatible? Do I need to get VS 2010 instead?
I want to execute some code in the MDI Parent Form when an MDI Child Form has been closed. What Parent Form Event would be best.
View 6 RepliesWhat I'm trying to do is your basic "You have made changes... yes/no/cancel" messagebox to show during a form closing event, and when they click cancel to stop the form from actually closing (Whereas yes would save and close, no would just close).
[code]...
I have two forms , first one is search and second is showing the data searched by first form search criteria. When the search query runs it takes lot of sql server resources, so I have passed that query to second form, it searches in database and shows the results. But if the results are not found I wish to close the second form in Form load event. As Second forms form load event searches for the record. I tried to use SecondForm.close in SecondForm.load event but failed to do so.
View 4 RepliesI have used the below code but its not showing the msgbox. What is wrong with this code ?
Private Sub frmSimple_Disposed(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Disposed
Dim result = MsgBox("Are you sure you want to Exit ?", vbYesNo)
If result = DialogResult.Yes Then
me.Close()
End If
End Sub
I have a combo box on a form. I have a SelectedIndexChanged event, that displays a message box when the combo box has another item from it selected. This works fine. However when the form is loaded, I initially want to set the current drop down box item from the database, then AFTER I have set the current value, I want this event to work. Problem is from the get go when the form loads it asks me the question as its being changed from 'no data' to then be populated with a bunch of data and an item selected.
[Code]...
I have a login form that when the user clicks OK and logs in successfully it loads the main application form.However when I show the main form and close the login form, the app is firing the shutdown event.Is this because the app thinks that the login form is the only form open and thus fires the shutdown event?Here is the code for the login routine, when I call Me.Close() at the end is when the shutdown event is fired. Am I doing things out of order? I used to do it this way in VB6 with no problems (I know they're a lot different).Note, it's nothing in frmMain either, this happens no matter what form I try to open.
Private Sub btnOK_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnOK.Click
'iLoginResult = 0 : Success
' 1 : Invalid user name or password
' 2 : Other login error
[code]....
I have a simple Windows Form that hosts property controls at runtime. When the user clicks Close [X] I want to keep the window and its contents alive rather than killing it by handling the FormClosing event, canceling the event and simply hiding the form.
That's fine but at close of the application I need to actually close the window. I implemented the below but it feels kludgey. Is there a simpler, more clever way to handle this situation? (The form's controller calls KillForm explicitly after it receives a closing event from the main window.)[code]...
I have a textbox control to take some input and a button to execute something. I want the button's click event will not work as long the validation to the textbox is successful.
Private Sub txtSuffix_validate(ByVal sender As System.Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles txtSuffix.Validating
If Not txtSuffix.Text = "" Then
[Code].....
Problem that you may have when dealing with two objects that are raising some events. Here, to make it obvious, I am closing the form, but the problem can be experienced with any other 2 classes event. First, what is the problem !
Let suppose that by pressing a button, you want to raise a custom event, then execute a method and then close the form
In that case, you may use a code similar to this
Event BeepIt()
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
RaiseEvent BeepIt()
[CODE]...
I am facing a issue while using the "validating" event of the maskedtextbox. I have an MDI form, in which there is a main form and a form acting as bottom bar. The bottom bar comprises of buttons for moving to "previous" and "next" forms. If suppose in the main form i have a maskedtextbox and the initial focus is set on it, then on the click event of the button (next; which is on the bottom bar form), it calls the validating event of the maskedtextbox twice. In the validating event of the maskedtextbox, i am checking some validations and if it doesnt pass, then i set [e.cancel = true]. just let me know the reason behind the triggering of "Validating" event twice?
View 1 RepliesI have a validating event for a txtbox called txtname. If the user tries to leave txtname for another txt box without entering their name a messagebox comes up giving an error. I have an exit button which will when clicked ask you if you really want to leave then you can choose yes or no. I can't seem to figure out how to allow the user to click the exit button while leaving the txtname blank so it would bypass the error message and only bring up the exit prompt. Here's what I have coded for the validating event and the exit event.
Private Sub txtName_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles txtName.Validating
If IsNumeric(txtName.Text) Then
[Code].....
In WinForms I could handle the Validated event to do something after the user changed text in a TextBox. Unlike TextChanged, Validated didn't fire for every character change; it only fired when the user was done.Is there anything in WPF I can use to get the same result, an event raised only after the user is done changing the text?
View 3 RepliesI have a datagridview and the cell gets validated in the validating event;
[Code]...
I have an application that has more than 20 text boxes used as inputs(numeric) ( in a form with multiple tabs), and from these numeric inputs I calculate many parameters and display them in other text boxes.The question is how can I trigger an event that will run the calculation procedures each time any of the text boxes numeric values change?( with out having to make procedure for each text box validated eventIs there some thing like a common validation event for any entry in any text box?
View 2 RepliesI have a validating event for a txtbox called txtname. If the user tries to leave txtname for another txt box without entering their name a messagebox comes up giving an error. I have an exit button which will when clicked ask you if you really want to leave then you can choose yes or no. I can't seem to figure out how to allow the user to click the exit button while leaving the txtname blank so it would bypass the error message and only bring up the exit prompt. Here's what I have coded for the validating event and the exit event.
Private Sub txtName_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles txtName.Validating
If IsNumeric(txtName.Text) Then
[Code]....
I designed a DataGridView under the name "dgvTarifa" and took a chance on trying Row Validating (tried Validated, CellEnter, CellLeave, RowEnter, RowLeave all count same) event. The purpose of the code is to load the selected values of the respective columns into three textboxes in order to rephrase/revalue those and update them by pressing a button. All works fine every single line of code there's nothing wrong except one logical thing.
When the form loads the RowValidating automatically fires because I have a function that Selects the table from the Database and it fills the DataSet by then attaching it to the datasourse of the "dgvTarifa" table. After setting the datasource of the datagridview, it automatically jumps to the RowValidating event which I DONT WANT TO! It first has to finish the whole function and later when the user enters with mouse or enters/leaves a row this has to be fired. (eventually already have the CellClick event with the same code below so only RowValidating has to work properly...)
Here's the code I use at row validating
Code:
Private Sub dgvTarifa_RowValidating(sender As System.Object, e As System.Windows.Forms.DataGridViewCellCancelEventArgs) Handles dgvTarifa.RowValidating
[Code].....
I am having a problem with the cellvalidating event constantly firing when the datagrid is refreshed (since the trigger that fires the event is the originally selected cell losing focus).I would like to remove the event handler for this at certain points of my code so that it does not fire but the examples I have come across on MSDN don't appear to do anything, so I guess I must be doing something wrong.[code]
View 1 RepliesWinforms, VS2008 I have a mainform that has 2 usercontrols: UC1 and UC2.UC1 has a treeview with treenodes. UC2 has tabControl with few tabPages. Selecting different nodes displays different details view in the TabControl's TabPages. What I need is canceling the event when the user has selected a node in the treeview, then he selects another node (i want to be able to cancel this last event:selecting another node, all depending on a certain logic)I mean: When the user is working on a tabpage in the tabControl, when he clicks on a different node in treeview (different from the currently selected node), before displaying the new node's details in the TabControl, I perform some logic, then depending on that logic, I set
e.cancel = true in the UC2 Validating event handler. (Rememebr UC2 includes the TabControl and the user, supposedly, has the focus on a control somewhere in TabControl)
But mysteriously, the event gets never canceled and the user still moves to the next node, displaying its details in the TabControl, although I set e.cancel = true.
I have a main form that has a button with which a smaller form is shown. Think of the smaller form as the Find/Replace dialog in many applications, such as Notepad. It's important that the form is (what I believe is called) modal. What I mean is that it always stays on top of the main form. I ensure that by calling the Show method with "Me" as the owner argument. Whenever the small form loses focus it will not disappear into the background but stay visible (albeit out of focus). If you don't understand open up Notepad and have a look at the behavior of the Find/Replace dialog.
Here's my problem: instead of actually closing the form when the X is pressed, I want it to simply Hide itself, so its position and the state of any controls (checkboxes etc) is preserved automatically.To achieve this I simply cancel the FormClosing event and Hide it:
vb.net
Private Sub Form2_FormClosing(ByVal sender As System.Object, ByVal e As System.Windows.Forms.FormClosingEventArgs) Handles MyBase.FormClosing
[code]....
To show the form, I use the following (note the (Me) to make the main form the owner of the form; this ensures that it remains visible even when it is out of focus):
vb.net
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Form2.Show(Me)
End Sub
Now. When I run my project, and open the Form2 (small form), then hide it again (by 'closing' it), I can no longer close the main form (Form1)! It seems the main form cannot close when the small form still exists (albeit invisible)...?? When I don't use the Me argument in the Show method, I don't get the behavior I want. I know I can set the TopMost property to True but that will also cause it to become visible on top of all the other forms, even windows not part of my application.