prevent deletion working erratically

[Jean-Pierre A. Radley]

I don't know why this was failing both at the customer's and here, since
I do recall seeing the same dates/filesizes on prc.input/tok.input at my
customer's and here.

When I told Doug that there was no @keyd label, I was wrong -- I must
have looked at prc.input in a totally different database.

To answer my own question: @keyd processing takes precedence over the
Y/N setting in a screen.  The @keyd processing was designed to forbid
the deletion of two particular special customer records, but procedding
to "DELETE" any other record.

Richard is right: @keyd is a lot more flexible, so now in addition to
@keyd preventing deletion of two particular records, I'll add a check
for @sn.

I ruefully and abjectly apologize for wasting everybody's time.

-- 
Yours Truly,
The Ironic Answerer
JP