Vb datagridview throws error when closing form

Question

1.00/5 (2 votes)

See more:

I have a VB windows form app with a datagridview. I changed one of the column types to a combobox, which works ok. However, when I close out of the form I get multiple 'datagridview default error dialogue' complaining about system.index out of range, one error for each row by the look of it.

No cell data was added or changed.

Any suggestions as to what might be going on?

What I have tried:

So, I found that the DataSet for the combo box, which is a "Lookup" that contains two fields, CustomerID and LastName has a parameter to toggle "Enforce Constraints". By setting to false, the error goes away. CustomerID is a key field.

Posted 29-Feb-24 21:06pm

Member 15485980

Updated 1-Apr-24 6:49am

v4

Add a Solution

Comments

Member 15627495 1-Mar-24 3:13am

without your code, we really can't fix your bug.
guessing is not possible... Vb code could be hundreds of methods/event/writing

please, show us the living code, target the lines about the bug.

Richard Deeming 1-Mar-24 4:01am

Agreed - no code, and only a vague hand-waving summary of the error rather than the actual exception details, means there is no way for anyone to help.

Graeme_Grant 1-Mar-24 5:56am

It sounds like you have hooked the form closing event and trying to process the DataGridView cells. you need to set a breakpoint in that code or break on all errors.

Graeme_Grant 1-Mar-24 5:56am

It sounds like you have hooked the form closing event and trying to process the DataGridView cells. you need to set a breakpoint in that code or break on all errors.

Member 15485980 31-Mar-24 22:59pm

I set various breakpoints around the form closing event with nothing that made any sense.

Graeme_Grant 1-Apr-24 0:09am

No code is posted and we can't see your screen from here. All that we can do is guess what is happening. If you want more help, you need to post code to reproduce the problem.

Member 15485980 1-Apr-24 12:28pm

There is no code, at least nothing that I created. I have a form load event to populate the grid, and a save click event, all of which are generated by the IDE. I didn't think it would be of any value to post that?

Graeme_Grant 1-Apr-24 18:47pm

How can you have no code when you claim that you are seeing an error? That makes no sense at all!

Member 15485980 2-Apr-24 12:42pm

I agree with you.
Thanks for the help..

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2024-02-29T21:14:00

We can't tell - we have no access to your code, especially not while it is running.
So, it's going to be up to you.

Fortunately, you have a tool available to you which will help you find out what is going on: the debugger. If you don't know how to use it then a quick Google for "Visual Studio debugger" should give you the info you need.

Use the debugger to identify where in your code the event is thrown, and from that find the event handler that is responsible. Put a breakpoint on the first line in the method, and run your code again through the debugger. Then look at your code, and at your data and work out what should happen manually. Then single step each line checking that what you expected to happen is exactly what did. When it isn't, that's when you have a problem, and you can back-track (or run it again and look more closely) to find out why.

Sorry, but we can't do that for you - time for you to learn a new (and very, very useful) skill: debugging!