ToshNeox, on 30 December 2011 - 11:52 AM, said:

Just buy a RJ-45 crimping tool and replacing the broken connector.

Why didn't you just buy a new cable?

RexGrammer, on 20 December 2011 - 12:23 PM, said:

I understand this is a matter of taste/religion but I actually prefer the use of prefixing private fields wrapped in properties with an underscore because it prevents naming collisions with variables in method scopes.

I caution you against creating properties (or any type of method) with side-effects. While you may not have any issues in some instances, it may come back to bite you as the code ages. But you should of course evaluate this on a case by case basis.

As this is mostly a matter of readability and maintainability, first ask your self which is more readable.

Player.IncreaseBalance(200)

Or

Player.Balance += 200

Lets say you've opted for dedicated methods to access your fields. First off, you you've already run into an issue because you've declared GetName as an int instead of an string. Yes the compiler will catch the mistake but it illustrates the point that by opting against the language feature of auto/explicit properties you're opening yourself up to bugs as well as making yourself think about how your classes work more than you should.

Side note: Its highly recommended to override ToString on most of your classes and your Player class is a prime candidate.

I'm going to head you off before you get too far down this path of madness, don't prefix your variable names with their type, the IDE will tell you what they are. Just give your variables meaningful names within the context of the problem your trying to solve.

What you're trying to do can be done many different ways but here are a few I came up with.

In this method I've combined the two statements into one DB call, added a parameter to prevent SQL injection and wrapped the sqlconnection and datareader in using statements so I don't have to manually close them.

using (var conn = new SqlConnection(@"Data Source=VAIBHAV-0EC092B\SQLEXPRESS;Initial Catalog=Navodayagiri;Integrated Security=True")) {
	conn.Open();
	var cmd = new SqlCommand("select Remaining_Dues from DuesMaster where Flat_No=@0;SELECT Name from HolderaNames where Flat_No=@0;", conn);
	cmd.Parameters.AddWithValue("@0", txtflatno.Text.Trim());
	using (var dr = cmd.ExecuteReader()) {
		if (dr.HasRows) {
			dr.Read();
			txtoutstandingdues.Text = dr.GetString(0);
			dr.NextResult();
			dr.Read();
			txtname.Text = dr.GetString(0);
		}
	}
}

In this method I'm making two calls to the DB but reuse the same Command object and connection.

            var conn = new SqlConnection(@"Data Source=VAIBHAV-0EC092B\SQLEXPRESS;Initial Catalog=Navodayagiri;Integrated Security=True");
            conn.Open();
			cmd.Parameters.AddWithValue("@0", txtflatno.Text.Trim());
            var cmd = new SqlCommand("select Remaining_Dues from DuesMaster where Flat_No=@0;",conn);
            txtoutstandingdues.Text = cmd.ExecuteScalar().ToString();
            cmd.CommandText = "SELECT Name from HolderaNames where Flat_No=@0;";
            txtname.Text = cmd.ExecuteScalar().ToString();
            conn.Close();

And my personal favorite is to use the amazing Simple.Data library.

var db = Database.OpenConnection(@"Data Source=VAIBHAV-0EC092B\SQLEXPRESS;Initial Catalog=Navodayagiri;Integrated Security=True");
var flatNo = txtflatno.Text.Trim();
txtoutstandingdues.Text = db.DuesMaster.FindByFlat_No(flatNo).Remaining_Dues;
txtname.Text = db.HolderaNames.FindByFlat_No(flatNo).Name;