So there is no primary key in the table? It's not difficult to delete duplicate records, but knowing which one to delete with a delete query is important. Here's some SQL to find your duplicate problems:
Code:
SELECT t1.ID, t1.Year, Count(*)
FROM MyTable as t1
GROUP BY t1.ID, t1.Year
HAVING Count(*) > 1;
That will find you all the particular cases in which you have duplicates. You'll have to replace the MyTable name and the field names with your real field names. By the way, "Year" is not a good choice for a field name, if that is really one of your field names. You should avoid reserved words and function names.
Hmmm.
Okay, Here's the easiest way I can think of.
First, create a play copy of your database.
Second, copy that one table, structure and data, to a backup name, still in the play database.
Third, delete all the data in the real (play) table.
Fourth, in design mode, establish a multi-column unique key on the fields that cannot be duplicated in that real (play) table.
http://stackoverflow.com/questions/2...cess-databases
http://bytes.com/topic/access/answer...que-constraint
Fifth, create an insert query to add the data back from your backup. The records which are dups will not be added back.
If that works, then you can do the same process on a work copy of your real database, after backing it up someplace safe.