StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20827850
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-12-29T17:11:53.073
FavoriteCount
0
LastActivityDate
2013-12-29T17:11:53.073
LastEditDate
LastEditorUserId
0
OwnerUserId
13302
ParentId
20827089
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I would suggest <ul> <li>using a <code>using () { ... }</code> block for your <code>SqlConnection</code> to ensure proper disposal of those objects</li> <li>use parametrized queries to avoid SQL injection attacks</li> </ul> So change your code to be: <pre><code>private void UserFullDetail_Load(object sender, EventArgs e) { string connectionString = "Data Source=PEWPEWDIEPIE\\SQLEXPRESS;Initial Catalog=master;Integrated Security=True"; DataTable dts3 = new DataTable(); using (SqlConnection SCScon = new SqlConnection(connectionString)) { string query = "SELECT cDetails, cDetails2, mainCate, PhoneNumber, PersonCharge FROM dbo.ComDet WHERE cName = @CName"; SqlDataAdapter daS = new SqlDataAdapter(query, SCScon); daS.SelectCommand.Parameters.Add("@CName", SqlDbType.VarChar, 100).Value = lblcName.Text; SCScon.Open(); daS.Fill(dts3); SCScon.Close(); } // get the first (and hopefully only) row from your DataTable DataRow firstRow = dts3.Rows[0]; // fill the values to your labels lblFirstDetail.Text = firstRow["cDetails"].ToString(); lblSecondDetail.Text = firstRow["cDetails2"].ToString(); lblCategory.Text = firstRow["mainCate"].ToString(); lblPhoneNumber.Text = firstRow["PhoneNumber"].ToString(); lblPersonInCharge.Text = firstRow["PersonCharge"].ToString(); } </code></pre> Of course, for your "real world" app, you'd have to add some checking and error handling (e.g. make sure the value in <code>firstRow["mainCate"]</code> isn't returning <code>NULL</code> - because in that case, calling <code>.ToString()</code> on it will cause an exception), but that's the basic mechanism of how your code should look like. And also, from an architecture point of view - I would strongly recommend to put all your database access code into a separate assembly that handles all of this work - don't put all this code into all your code-behind classes! 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POChanging Label based on SQL Server table data
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmarc_s
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POChanging Label based on SQL Server table data
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COi'll take a note.. thank you marc.. sorry about the previous action..
 singulars
 PostPostId
 PO
 UserUserId
 USMohd Nasrul Iwan Fajaruddin

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.