Database

Eddy Vluggen wrote:

he's asking how to identify them, I'm assuming that he doesn't want them.

Eddy Vluggen wrote:

No, you can't read it as you like; it depends on how it's used.

GenJerDan wrote:

After years and years and years of seeing things like this, I can almost guarantee that what I described is what was being looked for at this time.

Bastard Programmer from Hell

GenJerDan wrote:

Search for dupes. But they're not dupes as such.

GenJerDan wrote:

Yes, you can do that with a normalized database, too.

Bastard Programmer from Hell

Eddy Vluggen wrote:

Your assumption isn't logical, whether or not they are dupes (of the same
record) is determined by the key. It seems as if he's trying to find duplicate
records, not merely records that have the same value on a given attribute, isn't
it?
 

Select count(*), Name,Phone,Address from SomeTable 
Group By Name,Phone,Address
having count(*) > 1

enum ColumnName
{
    [System.ComponentModel.DescriptionAttribute("ID")]
    [System.ComponentModel.DescriptionAttribute("student_Id")]
    studentID

etc.
    studentName

etc.
    studentDetails
}

//So this indeed gets you the list.
OleDbCommand dbCommand = new OleDbCommand("SELECT * FROM tblUsers", this._dbConnection);

//Your reader then loops through the rows and you compare and check stuff

//Then you apply some logic, and determine what the values should be

//And then somewhere at the end of your reader loop you actually update your database like so:
OleDbCommand dbUpdateCommand = new OleDbCommand("UPDATE tblUsers " _
                                                "SET FieldOne = @ParameterOne " _
                                                ", FieldTwo = @ParameterTwo " _
                                                "WHERE KeyField = @ParameterThree ", this._dbConnection);
dbUpdateCommand.Parameters.Add("@ParameterOne", _
                            SqlDbType.NVarChar).Value = SomeVariableHoldingTheValueInQuestion;
dbUpdateCommand.ExecuteNonQuery;