Re: Stopping a 4GL Query

Path: emory!wupost!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!smfst2 From: smfst2@unix.cis.pitt.edu (Seth M Fuller) Newsgroups: comp.databases.informix Keywords: informix i4gl query Message-ID: <187415@unix.cis.pitt.edu> Date: 8 Oct 91 12:53:17 GMT References: <hlt.686852651@napcc> Organization: University of Pittsburgh In article <hlt.686852651@napcc> hlt@napcc (Harold L. Trammel) writes: >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. One thing that would work if you can construct your program this way would be to have the query loop in a seperate little 4GL program. This program would not have defer interrupt turned on and therefore would quit when the user hit the interrupt key. The parent program would call this program with a run statement. If you need to know a what row a user wants when they don't abort you could use a table that would contain the user's login name and the row number in the queried table. You would update this table in the query program when the user picks a row. The parent program could then query this table to go directly to the table the user wanted. If you wanted to use this tech- nique with multiple tables, you could add a field to your table for the table name queried. This is a little messy, but should work OK. Seth M. Fuller Giant Eagle, Inc. Pittsburgh, PA 15238 (412)963-6200