J
John Milbury-Steen
Hi Access gurus,
My database in Access 2002 is working just fine, thanks, except the
people who use it sometimes make redundant entries into an address list. (I
work for a university department and the address list is a list of all
prospective students session by session.) The problem is that prospective
students might apply more than once. The data entry people are supposed to
check whether a student has applied before, but sometimes they don't, so we
end up with two people named John Smith with the same social security
number.
How do I check that the new entry is really unique? That is, how do I
refuse the new record when it has a SS number matching an old one already in
the list? And, by the way, I don't do Visual Basic, I just do macros.
My database in Access 2002 is working just fine, thanks, except the
people who use it sometimes make redundant entries into an address list. (I
work for a university department and the address list is a list of all
prospective students session by session.) The problem is that prospective
students might apply more than once. The data entry people are supposed to
check whether a student has applied before, but sometimes they don't, so we
end up with two people named John Smith with the same social security
number.
How do I check that the new entry is really unique? That is, how do I
refuse the new record when it has a SS number matching an old one already in
the list? And, by the way, I don't do Visual Basic, I just do macros.