How about the simple "ignoring user responses" -- will that stop a
command-period cancellation whenever
it's the front-most process (the only time a command period should
invoke a cancellation anyway)?
That's a new one on me, Marc. (It results in a compile time syntax
error number -2741 here.) IIRC, valid attributes for considering/
ignoring statements are: application responses, case, diacriticals,
expansion, hyphens, punctuation, white space and numeric strings.
Alternatively, there could be a second TSR script that checks for
the first script's presence every x minutes
and relaunches it if it's quit, although I find that to be a very
poor solution.
The technique can be useful in some situations. However, in this
case, I'd probably try the FBA/error recovery mechanism routes first,
either to keep the app out of the user's way (if that's an option) -
or to trap a cancellation, so that an appropriate alternative action
(such as hiding the process) can be invoked. :)
