Re: defer interrupt.

>Did you read pages S-29 - S-32 (in the English version, anyway) of the >4GL 4.1 Supplement document? If so, what was unclear? Yes I've read them, but maybe theres something wrong with my configuration. In my test exemplar I'm interrupting a foreach loop thats fetching rows and getting some of them into a report. I started with 'whenever error call error_func' and when I hit ctrl-c the program goes to that function (usually with status = -213) and then goes to the int_flag check. I also tried it without the 'whenever' statement and then the prog. breaks right away with errors -229 and -103 (illegal key descriptor). So is it maybe something wrong with my termcap? Also one comment on the int_flag testing; if youre interrupting open, fetch, close statements (with something in between) do you have to test the int_flag after every statement (because you never know in loops where the ctrl-c will hit)? That seems like a whole lotta work for just wanting to be able to stop long queries. (config. I-Online 4.1, IBM/RS-6000 AIX 3.1) With thanks in advance Gaukur Disclaimer: Our god is what is left when every god has been counted and said: No, not him, not him. --Halldor Laxness.