Get data from database and display it on the grid ERROR

soonhuat81

I try to get the data from the database and then display it in gridcontrol, but it seems like not working.. I already created the dtArea table in dataset1, and here is the code i write : private void Form1_Load(object sender, System.EventArgs e) { sqlConnection1.ConnectionString = " .....MyConnectionString...."; sqlConnection1.Open(); sqlDataAdapter1.Fill(this.dataSet1, "dtArea"); sqlConnection1.Close(); gridControl1.DataSource = dtArea; } Whenever i run the program, the system stop at sqlDataAdapter.Fill(this.dataset, "dtArea") statement ... and the error message is as follwing: "An unhandled exception of type 'System.Data.SqlClient.SqlException" occured in system.data.dll. Additional information : System error " Can anyone help as i've tried so many times but still it's not working. Thanks in advance for the help.

6 Replies

Know the answer? Post it — somebody with the same question will find it here.

shl_tian22y ago
Maybe there is something wrong with the ConnectionString you can try it try{ sqlConnection1.ConnectionString = " .....MyConnectionString...."; sqlConnection1.Open(); sqlConnection1.Close(); } catch(SqlException es) { MessageBox.show(es.Message); } maybe in ConnectionString the password is null
miker22y ago
Look further into the SqlException to get meaningfull explanation of the error.
wdulker22y ago
Maybe there is something wrong with the ConnectionString
soonhuat8122y ago
I've check it, nothing wrong with the SQL Statement, it's the simple statements lik SELECT * FROM Area . That's it ... Anyone mind to check it for me i'll send it to ur email (just a simple project) . For ya info, i'm using the Microsoft SQL Server
abc22y ago
That usually means that there is a problem with your SELECT statement in the SqlCommand that is attached to your DataAdapter. Post that info as well. Tony
james22y ago
this problem has nothing to do with the datagrid, it is a problem with your data access. Most likely it is an error in your SQL statement. Try running the statement directly on the database. Also, the SqlException's InnerException property will generally give you a bit more information as to what the problem is. -James