How to handle the exception there is no row at particular position in C#

Question

1.00/5 (3 votes)

See more:

how to check for file extensions

What I have tried:

i am getting exception that there is no row at position 1 because my first dt has two rows second dt has one row and third dt has one row

Posted 8-Sep-17 1:16am

kav@94

Updated 8-Sep-17 2:30am

v3

Add a Solution

Comments

Graeme_Grant 8-Sep-17 8:14am

You're a help vampire. We are not your debugging service. You need to learn to use the debugger and read the error messages... the answer is there!

[no name] 9-Sep-17 9:22am

You should send code

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 · 2017-09-08T01:22:00

We can't tell - because we don't know which line it is, and we don't have any access to your data or code while it's running.

So, its going to be up to you.
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!