Click here to Skip to main content
15,885,365 members
Please Sign up or sign in to vote.
1.00/5 (2 votes)
See more:
lstvwTableList.ItemsSource = ds.Tables[0].DefaultView;


What I have tried:

private void tablezoneDatabind()
       {
           SqlConnection con = new SqlConnection(Globals.ConnectionString);
           string datetime = DateTime.Now.ToString("yyyy-MM-dd HH:mm:ss");
           DataSet ds = Globalvariables.Globals.select("select tablename from actbl");
           lstvwTableList.ItemsSource = ds.Tables[0].DefaultView;
           lstvwTableList1.ItemsSource = ds.Tables[0].DefaultView;
       }
Posted
Updated 17-Oct-22 3:58am
Comments
Richard Deeming 17-Oct-22 8:54am    
There's a secret error somewhere in your secret code. You need to fix that.

For a start, why are you creating a new SqlConnection object, but never doing anything with it?
Dave Kreskowiak 17-Oct-22 11:44am    
Why on earth would you put a method called "select" in "GlobalVariables"?

The problem seems to be your code is assuming the query worked and actually returned what was expected. You never check the result to see if it exists (is not null) before trying to use it.

1 solution

We can't directly help you - we have no access to your code (let alone while it is running) and no access at all to yoru data behind it. And you need both to even start working out what is causing the problem that generates the error.

The error is obvious from the message: there is no element at index zero, which means there are no tables in the dataset.

The problem is "why are there no tables?" and that needs the full code, the data, and the debugger working together with intelligent direction to work out.

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!
 
Share this answer
 

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