CompuServe Messages

Charles, I had/have exactly the same problem, but with my personal checkbook program. I also use it to record cash machine withdrawls, in which case I just want the 'checkNumber' field left blank. No way to test for the check number to be unique in that case. 🙁 I did solve it once by putting all my entry on a form, and using DML commands to test the 'uniqueness' of the check number when the user exits the record. That way the test was under my control. If a duplicate occurred I just told myself about it. A real kludge, however. And certainly not 'failsafe' when you really need to guard the integrity of the DB. Tim's reply sounds interesting, but I don't know that I want a bunch of garbage data in the field when it *should* be blank. Oh well. –jp–seattle–