C#

<br />
dtclass dt = new dtclass(value1, value2);<br />
dt.update;<br />

MyDatabase DB = new MyDatabase();//Data Context create by Linq to SQl

Car car = new Car();//Car class created by Linq to SQL
car.Make = "Ford";

DB.Cars.InsertOnSubmit(car);//add car to DB
DB.SubmitChanges();//Save DB changes

MyDatabase DB = new MyDatabase();

Car car = Db.Cars.Single(c => c.ID == 1);//get car based on ID value of 1
car.Make = "Citreon";

DB.SubmitChanges();//Save changes

class Person { ... }
class Car { ... Person Owner ... }

Person me = new Person(...) ;
Car mycar = new Car(...) ;
mycar.Owner = me ;

kruegs35 wrote:

When I think of organizing a list of people that have first names, last names, phone numbers, I think of a database table. I can store all the data in a table and query it to display what I need in a datagridview or whatever.

public enum PhoneNumberType
{
    Home,
    Mobile,
    Work
}

public class PhoneNumber
{
    private string number;
    private PhoneNumberType type;

    public PhoneNumber(string number, PhoneNumberType type)
    {
        // validate here
        this.number = number;
        this.type = type;
    }

    public string Number
    {
        get{ return number; }
    }
    public PhoneNumberType Type
    {
        get{ return type; }
    }
}

public class Person
{
    private string forename;
    private string surname;
    private List<PhoneNumber> numbers;

    public Person(string forename, string surname, IEnumerable<PhoneNumber> numbers)
    {
        // validate here
        this.forename = forename;
        this.surname = surname;
        if(numbers != null)
            this.numbers = new List<PhoneNumber>(numbers);
        else
            this.numbers = new List<PhoneNumber>();
    }

    public string Forename
    {
        get{ return forename; }
    }
    public string Surname
    {
        get{ return surname; }
    }
    public List<PhoneNumber> Numbers
    {
        get{ return numbers; }
    }
}

public class People : List<Person>
{
    // ToDo
}

erdinc27 wrote:

for (int i = 0; i < table.Rows.Count; i++)
{
cmd.Parameters.AddWithValue("@cek_no", System.Data.SqlDbType.NVarChar).Value = table.Rows[i][0].ToString();

cmd.parameters.add(\\add parameter name with datatype here);
Loop
{
   cmd.parameters["\\name of the parameter"].Value = \\Set value here.
}

treuveni wrote:

can someone please explain me what are the advantege and disadvantege of winforms vs. webforms.
When i rather to user one over the other.

Sathesh Sakthivel wrote:

If you use Winforms, you begin having a deployment problem. You either have
to have everyone update their machine everytime you update the application,
or you have to use ClickOnce. Depending on how complicated your application
and deployment scenario would be, clickonce may or may not be an option. You
will need to make sure your users have .NET 2.0 installed (clickonce can do
this for you, I believe). Because this is an internal application only and
will not be redistributed, it may be easier to implement this.