Printable View
I'm adding a combobox to a Winform and binding it to a dataset using the arrow menu on the combobox and stepping through the user interface. It auto populates the dataset, binding source and table adapter as normal. All of my comboboxes throw the same exception, but i'm not sure what is out of range:
A first chance exception of type 'System.ArgumentOutOfRangeException' occurred in System.Windows.Forms.dll
Does anyone have any insight to this?
Can you share your code please?
There's not any code, it's all done in the combobox menu. Click the small arrow on the upper right corner of the combobox and bind to a DataSet, select the Display Member, select the Value Member from the pull-down menus and run the application.
This happens on every bound combobox in my application. The dataset populates the combobox values just fine, it just throws this first chance exception and I'm not sure why.
There has to be code, the tableadapters have to fill the datatables when the form loads. Look in the form_load event. Also, you put that code inside a Try/Catch block and maybe it will give you a better explanation of the error.Quote:
Originally Posted by Fedaykin
Here is the auto-generated code from the binding the combobox. I added a Try Catch as suggested but it did not catch any exception, and yet a first chance exception was generated in the Immediate Window:
Code:Private Sub Form81_AcctProjectCost_Load(sender As Object, e As EventArgs) Handles MyBase.Load
'TODO: This line of code loads data into the 'SalesEmpNameds.EmpName' table. You can move, or remove it, as needed.
Try
Me.EmpNameTableAdapter.Fill(Me.SalesEmpNameds.EmpName)
Catch ex As Exception
MessageBox.Show(ex.ToString)
End Try
End Sub
When does the exception occur? When you start the program, when the form load, when you click on the combobox. The IDE usually stops on the line of code causing the error.
So are all the comboboxes filled by the same datatable?Quote:
This happens on every bound combobox in my application. The dataset populates the combobox values just fine, it just throws this first chance exception and I'm not sure why.
The error occurs when the form loads, specifically when the Me.EmpNameTableAdapter.Fill(Me.SalesEmpNameds.EmpName) runs.
No, all comboboxes are filled by various different datatables. The example I gave here is a very simple one. Like I said before the data loads into the combobox without any hitch and since this is a First chance exception the debugger doesn't stop it and a Try Catch doesn't catch it. It's very strange.
Okay the plot thickens:
When I fill the combobox at form load this error:
A first chance exception of type 'System.ArgumentOutOfRangeException' occurred in System.Windows.Forms.dll
When I close the form with a Me.Dispose() this error:
A first chance exception of type 'System.Data.EvaluateException' occurred in System.Data.dll
If I comment out the, then no error occurs.Code:Me.EmpNameTableAdapter.Fill(Me.SalesEmpNameds.EmpName)
The dataset query that's embedded in the Edit Query UI in Visual Studio looks like this
I appreciate you guys helping me dial this in.Code:SELECT wholename FROM dbo.EmpName WHERE Salesperson = 1
I don't have an answer for you but I would suggest a couple of things. When you post your code, post the actual code and not just part of it. So if there is more code in your Form_Load event post all of it. Also, there is no need for the Me.Dispose, if you want to manually close the form then us Me.Close.
As I've repeatedly stated, there is no other code, the complete code is posted above in the formload event, the code is a single line auto-generated by Visual Studio when you bind the combobox. Both Me.Close and Me.Dispose yield the same result. Both errors are eliminated if I simply comment out the single line of code that fills the combobox.Quote:
Originally Posted by wes4dbt
I only added the Try Catch to try to get more info about the error, but it doesn't catch anything.
Quote:
No, all comboboxes are filled by various different datatables. The example I gave here is a very simple one.
If there is more than one datatable then you have more code.Quote:
As I've repeatedly stated, there is no other code, the complete code is posted above in the formload event, the code is a single line auto-generated by Visual Studio when you bind the combobox.
Anyway, maybe someone else can figure out what's going on. Good luck
the only thing that comes to my mind is that maybe your combo doesn't have all of the values it's trying to bind to.
Ex: the DT for the combo hold 1,3,5,6,7... but the record that it's trying to show has a value of 2 ... so it doesn't exist in the combo.
-tg
That's what the error message 'System.ArgumentOutOfRangeException' would have me believe as well, but I'm not searching for a value before the query and everything present in the database ends up in the combobox.Quote:
Originally Posted by techgnome
The other error message 'System.Data.EvaluateException' occurred in System.Data.dll when the form closes is equally baffling.
If i comment out the combobox fill both error messages no longer appear, so that's definitely where its occurring. I'll try some other stuff to see if i can shake something loose. Thanks for everyone's responses.
I would suggest this first, move the code in the Form Load event to a separate sub and then call it with a button or something else. The reason I say this is because depending on your architecture configuration, for some reason, when an exception occurs in the load event it just jumps out without catching it.
Are any of the properties for the combobox, like DisplayMember, ValueMember or SelectedValue set to any other than "wholename", sense that's the only column in the datatable? If they are set to anything that's not in the datatable that could throw an error.Code:SELECT wholename FROM dbo.EmpName WHERE Salesperson = 1
Also, when you bind your control using the designer, you assign a data member and a value member (optional). Are you setting both? if so, what fields are you selecting for them?
How about SelectedValue?
You may not have written any code, but code was generated in the designer files that does the selection. That's where I suspect the problem might be...Quote:
Originally Posted by Fedaykin
You can set breakpoints in the designer file, then step through it, see if the error happens in there.
-tg
I realize this post is old but I figured others may have this issue and this may help. I had had the same issue...multiple "first chance exceptions" being thrown during the call to fill the dataset. Try the following:
SomeBindingSource.SuspendBinding
SomeTableAdapter.Fill(SomeTable)
SomeBindingSource.ResumeBinding
That keeps the control from doing work while you load data. Obviously you may need to do mulitple suspends then fills then resumes depending on your data. On some forms designs the exceptions caused no problems for me. But on one of my forms I had a self-referencing table (parent/child) with a combo box and the behavior was strange. Editing the first row in the dataset caused the combo to point to the first record regardless of the proper data while editing any other record would produce the correct behavior. Once I suspended, filled, and resumed the exceptions went away and everything worked properly.
I hope someone finds this useful.
Dennis