Is there a way to prevent the form closing event from executing if validation fails on a control? If validation on a control fails this stops the form from closing, but the closing event still executes. Scenario is user has focus in a text box, tries to close the form. Validation fails, but closing event is fired. I'm not sure how I can abort that event.
View 5 RepliesI am using validating procedures to validate user input from 4 text boxes. I am experiencing an issue using the 'x' button to close my form if invalid or no data is present in the textbox with focus when I click the 'x' button. Validating triggers and the message box appears. You can change the data to something valid and close fine but this is aggrevating. I changed the forms causevalidation attribute to false and created a sub to handle formclosing. In that sub I specified that causevalidation for all textboxes be disabled and also set e cancel to false. After that I tested with bad data and the message box showed again, but when I closed it the form closed also.
View 4 RepliesDim frm As Form
For Each frm In Forms
Set frm = Nothing
Next frm
The above code is what I used in VB6 to close all forms associated with my programs before my program closed. I have been searching for information on how to make sure all forms are closed when closing a VB2008 program.
I have seen info on using the Project Property Shutdown mode When startup form closes and I currently have this set.
Is this all that is really necessary? Will the garbage disposal close everything else to free up RAM?
Also, if I have several forms open and want to close all from the main form without closing each one individually, what is the best approach? Is there a collection like in VB6, go through the collection, compare it to the name of the main form and close it if it is not the main form?
I'm trying to use the events Validating and Validated on a ToolStripTextbox.
Private Sub txtMenuOwnIP_Validated(ByVal sender As Object, ByVal e As System.EventArgs) Handles txtMenuOwnIP.Validated
MyIP = txtMenuOwnIP.Text
StatusLabelIP.Text = MyIP
End Sub
[code].....
Neither code is firing.The CausesValidatition of the txtMenuOwnIP is set to true.I can enter stuff into that Textbox and leave it using the Mouse or simply piush Enter, but the posted code won't get fired (used a Breakpoint in both subs). There are no other event routines for this command used.
For example, is this an acceptable way of checking that fields are not empty before submitting data to a datatable/database? Right now, Im simply checking with an If statement, and I'm starting to think that this is not the correct way to do it.
I'm also trying to learn more about unit testing, so if you have any tips or tricks, please feel free to share.
[Code]...
Here's what I'm trying to do:I have a top level form which is an MDI container. I have a subform which contains property controls that might be used to make changes to "document" subforms. There is exactly one instance of the property form, which is either shown or hidden, but never actually closed.Show/hide from a menu seems easy enough: I have a menu item, which when triggered toggles the show/hide state and changes the "checked" state of the menu item (also used to determine whether the subform is currently shown).
The problem I'm having is that I also want to catch the "close" event for the subform, and cause that to hide the form and then cancel the close event.What actually happens is this: the event handler catches close events not just from the subform, but from the parent form as well. So I can get the function that I want, but it also prevents the parent application window from being closed.How do I catch just the subform event and not the parent form?Here's a representative section of the code that I have (bear in mind that I've been trying different things here, so there may be some odd things that I've broken):
Public Class Example
Private WithEvents PropertiesForm As New Properties()
Private Sub Example_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)
[code].....
I have a very simple app working well, problem is that it does not close properly. If the user uses the little "X" to close it, it still remains running, just becomes invisible. The X does not fire the closing/closed events..All I can figure out is that to get it to properly close I need to use "Me.Close()" with a button or menu item.I could remove the standard X and force them to use my own close button but that is rather silly..
View 1 RepliesI'm running a program, the first form is a login form. If you pass this i Hde form1 and show form2.When i'm click the x in the top right hand corner my form goes away but in my processes (task manager) it's still there. why?
View 9 RepliesI have 2 forms. When a user clicks something on form1, form2 pops up. After user is done with form2 and closes it (where the dataset is updated), I want form1 to "reload" the dataset to reflect changes made in form2.
View 1 RepliesI have the following code to close a form which is a child. The problem is that when it closes, it closes the MDI parent too.
Private Sub frmTransaction_Closing(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles MyBase.Closing
If ListView1.Items.Count >= 1 Then
[Code]....
What function would i use to cancel the form from being closed via them pushing the "x" in the top right?Basically want it to hide the form, set showintaskbar to falseand then display the notifyicon. Which all I know how to do, but cant quite seem to figure out how to stop the form from being closed.
View 2 RepliesI am working on a program and for some reason when I run it as an executable outside of debug mode, if I run the main subroutine of the program, the process remains in memory after being closed. Even though the form is closed/gone, it will be in the process list and I have to ctl-alt-del to remove it. If I exit right after opening the form without doing anything, it closes like normal. I am closing and disposing everything I can think of, and I've never had this problem before. This is how I am exiting, but the problem also occurs if the user "X's" out.
Me.Close()
Application.Exit()
I have a couple web file requests in my program, which is the only thing out of the ordinary (code-wise) for me, don't know if those are the root of the problem. I can't imagine this is the first time this has happened to anyone, but I couldn't find anything helpful with my search terms. Any ideas/common solutions? I can post sections of my code if it will help, but the whole thing is pretty long and I couldn't narrow down any potential problem areas.
1. I am closing the form which started the thread inside the thread. There are no errors , but Is it safe ?
2. The thread starts at click of a button . If same button is clicked again , the thread is aborted. Should the thread be made Background or foreground ? it is working either way.
my code :
Private Sub BtnOk_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BtnOk.Click
m_Thread = New System.Threading.Thread(AddressOf MyFunction)
m_Thread.IsBackground = True
[code]....
How can i actually reload a form without actually closing it and re-opening it?By using a button click?
View 34 RepliesVS 2008 Finding the reason a form is Closing
View 1 RepliesI have a modal form that does double duty.When a user wants to add a new object to a database, I open the form blank and they fill it out. When the form closes, all of the data is passed back to my main form and is used to create the new object in the database.When a user wants to edit an existing object, I open the form and pre-populate all of the fields with the object's data.I'm running checks on the form as they edit the fields, only enabling the "OK" button (which will update the database) if the form has actually been changed. If they make a change and then undo it, the "OK" button is reset to Enabled = False.At the bottom of the form are a ComboBox, two buttons and a ListBox. The intent is to allow the user to select an item from the ComboBox and "Add" ("Add" button) to the ListBox, or select an item in the ListBox and "Remove" ("Remove" button) it FROM the ListBox.
This function works fine when the form is loaded blank.When the form is loaded with data, however, (and in the testing I've done, the ListBox has no items in it to start, which is valid), adding an item from the ComboBox to the ListBox causes the Modal form to close with a DialogResult of Cancel.I've tried to trace the source of this issue, but stepping through each line in debug mode gives me no clue as to why this is happening.I COULD remove all of the checks and update the form each time the user presses "OK" (in the case of no changes, the database data would be overwritten with the same data), but that seems kludgy and less elegant. Plus, I'd like this logic to work.
Is there any way I can find the exact reason a form is closing ? To be more specific , I'd like to find when a form is closing :1) because the user pressed the X button on the upper right corner2) due to code (Me.Close , MyForm.Close etc)I know I can use the FormClosing event and use this code :If e.CloseReason = CloseReason.UserClosing Thenhowever it seems that the CloseReason.UserClosing catches both cases (closed by te X button or by code) . So , is there any way I can find exactly the reason a form is closing ?Back in VB6 , the correspondent UnloadMode variable of the Form_Unload event could be "vbFormCode" which indicated specifically that the form was closed by code
View 4 RepliesHow do I revert a form including the controls back to a original state without closing the app? For example I got a picture box and 2 buttons in a form..
[Code]...
Load , Initialize , Activate . What's the difference among them ? Up to now I was used to the classic VB6 events , but it seems that in .NET they are different . I was used to these ones :Load / Initialize : both the first step before showing a form . One appeared in VB6 , the other in VBA .Activate : triggered when a form is selected .However I thing that now , not only they differ , but they also come in a different order ...
View 34 RepliesI am trying to close my application and I have coded on the form closing, form closed events to call an exit form which asks the user for confirmation to exit or not. All works fine. When I press the X button on the winform things act different. On the main form where I press the X btn I store some user ID data that I use throughout the app. If I press cancel on the exit form that data is lost from the main form and cannot be used afterwards. So if the user pressed by mistake the X btn and then presses cancel on the exit form the application loses some stored data and many functions stop working.
View 4 Repliessetting the form opacity programatically in the MouseEnter and MouseLeave events.The problem isn't with the actual events, the problem is that the events occur in places where I don't want it to happen.So in my project, I have a form with 3 user controls in it. The user controls are docked in the form so no actual space from the form is available to the user.
I have the methods:
Form1_MouseEnter(~) Handles Form1.MouseEnter, UserControl1.MouseEnter, UserControl2.MouseEnter, UserControl3.MouseEnter
Form1_MouseLeave(~) Handles Form1.MouseLeave, UserControl1.MouseLeave, UserControl2.MouseLeave, UserControl3.MouseLeave
when you enter the form, the form opacity is set to 1. And when left, the form opacity is set to 0.7 .However, what happens right now is obviously that when the user changes the mouse position from one user control to another, the form opacity flickers (turns to 0.7 and back to 1 really fast).
I have an application has a data entry form, and currently I'm using the form validation and validated events to validate the data - along with an error provider. I've read that this logic should be placed in the Dataset rather than the form. To that end, i've started exploring how to do that.
[Code]...
I have googled high and low to find an answer to this but I must be searching wrong.I have an application which has a listview displaying some items that are stored in a SQL Compact database. I am using a second form to add new items to this list directly into the database.When the second form closes I want to call the sub in my first form to refresh the list from the database.
How can I get it to fire the form1 sub routine on the close event of form2
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 RepliesWe 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 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.
In my .NET porject, I have to run a lot of validation on 4/5 fields. This validation checks if certain fields have errors, for example: the name field is not allowed to have numbers or symbols. If all these checks are passed, I need to execute a SQL query to pull some data out of the database. I could have it with a lot of nested IFs, and run the function at the end once it passes them all, but this will translate into about 12 nested IFs, and it seems a really bulky way to do it. I have also thought about setting a boolean value after every check, and if the value is 1 then don't run the function, else do. But of course this gets overwritten by other checks that pass.
View 2 RepliesAlright, I have a vb6 LEGACY application and new Functionality (Form) written in c#. I have a VB.NET COM Class as a wrapper. I can launch the .NET Form just fine. THe problem I am having is closing the .net form from vb6.
Example:
In VB6, I have something like this:
CODE:
But it does not work becuase frmViewer is Nothing for some reason. how I should close the .NET form that was launched from VB6?
I have a parent form that has a list of items and each item has a unique ID. The user can open one or many of the items in a child form (it is set up in a tabbed MDI), but it can only open one instance of each item at a time.
In the parent form, I was going to make a collection (or something like that, maybe there is a better way) to keep track of which items are open in the child forms. I need to know when each child is closed so that it can be removed from the collection and reopened at a later time. I was thinking that when the child form closes, it somehow does something (like raise an event) that tells the parent form to remove the unique ID from the list of current open child forms.
My questions are, is this a good way to do this and I am pretty sure I would use the form closed event in the child form to update that parent form, but as well, I didn't know if this is the best way of handling it.
If raising the event is a good way, are some examples on how to do it out there? I found some for controls, but not while the form is closing/closed.
Im Using VB 2008. I have MsgBox() statements in all Mouse & Form Click events to TEST & NOTHING FIRES during Form Load when I click on Form or Button Controls !!! The Form Load event contains code for Displaying the Label.Text control many times with changes in the Text to simmulate annimation.
[Code]...