The safest way, IMHO, would be to define a rule in the table that restrict duplicates for this field. If TableUpdate() return .F., use AError() to detrmine why. That way, if 2 users tries to add the same value at the same time, only one of them will succeed.

HTH

---

>This seems line an elementary question, but it's got me a bit puzzled. When the user is entering a new record, how do you check to be sure a field doesn't have a duplicate value without moving the record pointer? This also would have to take into account buffering. It seems as though I've done this before, but my head is in a bit of a muddle today and it's not coming to me.