Re: What Do ???????????????

In article <1165@pdxvme.pdx.csd.mot.com>, donb@pdx.csd.mot.com (Don Bolton) writes: .... |> CAN the KEYs be trapped and "nulled"? Ie: if before delete logic sez no, |> then DON"T LET THE DELETE KEY PASS GAS? Here's what I would do: 1) Use the options statement to change the delete key to something obscure (preferably untypable). 2) put an ON KEY clause in your INPUT ARRAY, to trap the key that you want use for delete. 3) Implement the delete operation yourself, with whatever tests and safeguards you need. If delete is ok, you can move up the remaining rows, adjust the count, etc. using your own code. BUT, you ask, HOW do I let INPUT ARRAY know what I've done? It's easy: exit from the INPUT ARRAY first, do what you need to do, and then reenter it. BUT, you ask, HOW do I get back to the row the user was at before? You've already seen the answer: |> And yes I took a stab at the WINTER 90 WHILE TRUE/EXIT/SCROLL tech note, its a |> good thing I didn't step in it. :-) This technique is roundabout, tricky, and indispensable if you need to do complicated things with arrays. At least, if some one can recommend a better approach, I'd like to hear about it. Seriously, I've used this approach to do what you seem to be aiming at, and more. It's painful the first time, but you get the hang of it after a while; IMHO it's much better than mucking around with undocumented internal variables. -- Harry Bochner bochner@das.harvard.edu