Larry,

>> Actually, I have looked at it ( a little :) ) and my reason for avoiding it is that APPEND BLANK violates the key's 'uniqueness' and so triggers an
error. Lately, though I haven't been using the APPEND BLANK method, so maybe I'll revisit this issue. <<

I know how you feel hear to, when trying to take advantage of a feature you discover it interferes with/requires/changes behavior of some other feature. So you look into that one and it happens again. As Pee-Wee Herman said so well, "It's like you're unravelling a sweater that someone keeps knitting, and knitting, and knitting...."

However, in this case I can say that if you look into Buffering at least, you can take advantage of Primary Keys. Defaults will also help, but are not required.

Using buffering, you can insert anything. You then have something like this in code:

[User clicks Save:]
IF ! TableUpdate()
=Messagebox("Sorry, guy, there's something wrong here...")
ENDIF