prevent multi field dupe

  • Thread starter Thread starter deb
  • Start date Start date
D

deb

trying to prevent dupes.
access 2003
want to prevend dupe if ProjectID, UnitNo, KeyMilestonesSubID, ActualDt are
the same.

I setup index and it works except if UnitNo is blank, it will allow dupes in
the other fields.


any suggestions?
 
If you make that combination the primary key, it wouldn't allow dupes.
However you couldn't have the UnitNo blank there either.

Have you considered populating the UnitNo field with something bogus like a
0? That would allow using a unique index to keep out dupes.
 
Back
Top