Stopping a 4GL Query

Path: emory!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!napcc!hlt From: hlt@napcc (Harold L. Trammel) Newsgroups: comp.databases.informix Summary: How can you stop a constructed query in i4gl? Keywords: informix i4gl query Message-ID: <hlt.686852651@napcc> Date: 7 Oct 91 16:24:11 GMT Sender: usenet@ux1.cso.uiuc.edu (News) Organization: University of Illinois at Urbana My users will frequently begin either an on-screen "CONSTRUCT"ed query or a prompt driven report with wild cards or other entries that sends the application off to check every row in the database. I have an "ON KEY" routine that works before the query or report actually begins. Our problem is after the report begins. As far as I can tell from the I-4GL docs, ON KEY works with INPUT, INPUT ARRAY, and PROMPT. Checking the int_flag setting is stated to be ok with the above three and CONSTRUCT (7-66R). I have tried to insert an int_flag check routine into cursor management loops. This gave errors, but I do not have the specific one in front of me. Any suggestions? Perform does it. The query language does it. How do I do it with my application? BTW: I'm running I-Turbo, I-SQL, and compiled I-4GL on a Sequent Balance 8K. I doubt that has anything to do with it. Thanks! ======================================================================== Harold L. Trammel | hlt@napcc.cvm.uiuc.edu National Animal Poison Control Center | (128.174.187.6) College of Veterinary Medicine | University of Illinois Urbana-Champaign | Urbana, IL | ========================================================================