Datagridview isn't always filled

Question

1.00/5 (1 vote)

See more:

I'm currently working on a project wheere, for each category and subcategory of my products, I need to do some inspections. Here's how my winforms works:

1.I click on the first combobox which indicates categories :

https://i.stack.imgur.com/lzFIX.png[^]

2. I select a subcategory on the second combobox

https://i.stack.imgur.com/zsOta.png[^]

3.The datagridview is generated, and generates with itself some data measure samples. Depending on the inspection criteria, I get 1,3,5 or 7 measures. I get the maximum number of measures n, then generate columns n times, and do not give the right to n-k columns for each k<n.

<a href="https://i.stack.imgur.com/xF0i1.png">https://i.stack.imgur.com/xF0i1.png[^]

What I have tried:

The issue I'm facing is that, it only fills the first time, and not the other times. Can anyone please help me out with it?

Posted 26-Jun-23 21:32pm

LiterallyGutsFromBerserk

Updated 6-Jul-23 0:48am

v2

Add a Solution

2 solutions

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 · Accepted Answer · 2023-06-26T21:52:00

First off, never concatenate strings to build a SQL command. It leaves you wide open to accidental or deliberate SQL Injection attack which can destroy your entire database. Always use Parameterized queries instead.

When you concatenate strings, you cause problems because SQL receives commands like:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'Baker's Wood'

The quote the user added terminates the string as far as SQL is concerned and you get problems. But it could be worse. If I come along and type this instead: "x';DROP TABLE MyTable;--" Then SQL receives a very different command:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;--'

Which SQL sees as three separate commands:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'x';

A perfectly valid SELECT

SQL

DROP TABLE MyTable;

A perfectly valid "delete the table" command

SQL

--'

And everything else is a comment.
So it does: selects any matching rows, deletes the table from the DB, and ignores anything else.

So ALWAYS use parameterized queries! Or be prepared to restore your DB from backup frequently. You do take backups regularly, don't you?
You may get away with it at the moment if the Combo boxes aren't user editable, but when someone requests a change in six months time, are you going to remember that code? Always use parameters!

Secondly, Without you DB there is no way we can run that chunk of code to try and work out what might be happening - there is too much data dependence in there with all the "magic strings" for it to be viable for use to duplicate your problem.

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.

Put a breakpoint on the first line in the function, and run your code 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!

LiterallyGutsFromBerserk · Accepted Answer · 2023-07-04T04:30:00

As OriginalGriff said in their comment, the solution to this issue is to simply edit the formatting from the cellformatting method in order to avoid changes being overridden.

In my own case, I declared an global integer "numColsGen"(number of columns generated),which helped me know how many columns I had generated. Then, in cell_formatting, depending on b's value, I formatted my cell in a certain way.

Here is the code to it :

C#

if (numColsGen== 5)
            {
                if (dataGridView2.Rows[e.RowIndex].Cells[$"donnees{comboBox1.Text + comboBox2.Text}DataGridViewTextBoxColumn"].Value.ToString() is "1")
                {
                    if ((dataGridView2.Columns[e.ColumnIndex].HeaderText is "Donnee2") || (dataGridView2.Columns[e.ColumnIndex].HeaderText is "Donnee3") || (dataGridView2.Columns[e.ColumnIndex].HeaderText is "Donnee4") || (dataGridView2.Columns[e.ColumnIndex].HeaderText is "Donnee5"))
                    {

                        e.CellStyle.BackColor = System.Drawing.Color.Gray;
                        dataGridView2.Rows[e.RowIndex].Cells[e.ColumnIndex].ReadOnly = true;


                    }
                    else if (dataGridView2.Rows[e.RowIndex].Cells[$"donnees{comboBox1.Text + comboBox2.Text}DataGridViewTextBoxColumn"].Value.ToString() is "3")
                    {
                        if ((dataGridView2.Columns[e.ColumnIndex].HeaderText is "Donnee4") || (dataGridView2.Columns[e.ColumnIndex].HeaderText is "Donnee5"))
                        {
                            e.CellStyle.BackColor = System.Drawing.Color.Gray;
                            dataGridView2.Rows[e.RowIndex].Cells[e.ColumnIndex].ReadOnly = true;
                        }
                    }


                }
            }

Thanks for your help and post, OriginalGriff!

Datagridview isn't always filled

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0