>For example, assuming something like "syntax error" or "not a table" occurs in an isolated procedure called, say, from a menu item, then in many if not most cases I certainly can "recover successfully programmatically" by issuing a warning to the user and then calling RETURN TO Mainloop in my error handler,
>
>I see that what you mean by recover is different from what I mean by recover < s >. By recover, I mean that issuing a RETRY would allow the procedure to execute successfully (such as in the case of "Printer off line"). I suppose the question could be phrased better.

I see what you mean.

>So, tell us, what's the scoop behind the rest of the questions? <g>
>
>What do you mean by that? You want the answers? I am sure you know them < s >

Well, I know the answers assuming I understand what you really asked.

I think I do, anyway. <g> Except for LISA. I believe I'll go surfing for that one.

Number 3 took me a while. Not to get the answer; I just ran the code. To figure out *why*. Talk about trick questions. <g>