Hi:
I have a table with test data that includes ID numbers. The ID number is the primary key. However, these ID numbers do not take the current year into account. So, my problem is that when the same number from last year is keyed in this year, there is a primary key violation.
One idea to combat this was to create another field in the table, "Year", and fill the current year in that field. Then, I could possibly have Access look at the combination of those two fields, "IDNumber" and "Year" to determine key violation or not.
Could someone please tell me if this is feasible or not? Thanks a lot. I really appreciate the help.
Daniel Pope
I have a table with test data that includes ID numbers. The ID number is the primary key. However, these ID numbers do not take the current year into account. So, my problem is that when the same number from last year is keyed in this year, there is a primary key violation.
One idea to combat this was to create another field in the table, "Year", and fill the current year in that field. Then, I could possibly have Access look at the combination of those two fields, "IDNumber" and "Year" to determine key violation or not.
Could someone please tell me if this is feasible or not? Thanks a lot. I really appreciate the help.
Daniel Pope