Click here to Skip to main content
15,891,136 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
if (cn.State.ToString() != "Open")
         cn.Open();
     cmd = new SqlCommand("select BARCOD from INCREMENT_MADA where BARCOD='" + t1.Text + "' and NAME_TECHARE='" + comboBox1.SelectedItem.ToString() + "' and NUMBER_QAEMA='" + t10.Text + "' and NMAE_MSHTARK='" + com_mada.SelectedItem.ToString() + "'", cn);
     dr = cmd.ExecuteReader();
     bool bl = dr.Read();
     dr.Close();
C#



What I have tried:

C#
if (cn.State.ToString() != "Open")
                    cn.Open();
                cmd = new SqlCommand("select BARCOD from INCREMENT_MADA where BARCOD='" + t1.Text + "' and NAME_TECHARE='" + comboBox1.SelectedItem.ToString() + "' and NUMBER_QAEMA='" + t10.Text + "' and NMAE_MSHTARK='" + com_mada.SelectedItem.ToString() + "'", cn);
                dr = cmd.ExecuteReader();
                bool bl = dr.Read();
                dr.Close();
Posted
Updated 1-Feb-18 1:29am
Comments
F-ES Sitecore 1-Feb-18 4:59am    
This question is asked multiple times a day, please do basic research before asking a question like using google. When you get an error always say what line it is on, no-one can help you with the little information you've provided.
Karthik_Mahalingam 1-Feb-18 4:59am    
in which line you are getting the error?
use break point to debug the null value.
Richard MacCutchan 1-Feb-18 5:17am    
And while you are at it Google "SQL injection", to learn why that code leaves your database wide open to corruption or destruction.

1 solution

This is one of the most common problems we get asked, and it's also the one we are least equipped to answer, but you are most equipped to answer yourself.

Let me just explain what the error means: You have tried to use a variable, property, or a method return value but it contains null - which means that there is no instance of a class in the variable.
It's a bit like a pocket: you have a pocket in your shirt, which you use to hold a pen. If you reach into the pocket and find there isn't a pen there, you can't sign your name on a piece of paper - and you will get very funny looks if you try! The empty pocket is giving you a null value (no pen here!) so you can't do anything that you would normally do once you retrieved your pen. Why is it empty? That's the question - it may be that you forgot to pick up your pen when you left the house this morning, or possibly you left the pen in the pocket of yesterdays shirt when you took it off last night.

We can't tell, because we weren't there, and even more importantly, we can't even see your shirt, much less what is in the pocket!

Back to computers, and you have done the same thing, somehow - and we can't see your code, much less run it and find out what contains null when it shouldn't.
But you can - and Visual Studio will help you here. Run your program in the debugger and when it fails, VS will show you the line it found the problem on. You can then start looking at the various parts of it to see what value is null and start looking back through your code to find out why. So put a breakpoint at the beginning of the method containing the error line, and run your program from the start again. This time, VS will stop before the error, and let you examine what is going on by stepping through the code looking at your values.

But we can't do that - we don't have your code, we don't know how to use it if we did have it, we don't have your data. So try it - and see how much information you can find out!

And do yourself a favour: 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. Use Parametrized 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?
 
Share this answer
 
v3

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900