Re: New Era Prblemette

I think the best thing you can do is make use of the <superTable>.rowRetrieved event. This event is posted every time after a row is fetched from the database. The handler for this event could implement the logic to stop the retrieve. On page 3-367 of the 'Graphical and Connectivity Reference Version 2.0' there are more details. Success, Henk Vandana R. Chadha wrote: > > > Whenever we have used SQL interrupt on and then cancelled, the data > connection gets lost. Have u found a soln to that? > > Vandana > ______________________________ Reply Separator _________________________________ > Subject: RE: New Era Prblemette > Author: "Derumier David" <david.derumier@trasys.be> at aflgate > Date: 7/2/98 2:40 PM > > > In NewEra 2.20, we use the setCancelMode, setCancelTimeout, ... method of > ixSQLconnect class (not for ODBC connection, only with informix inet > connection). > > David Derumier > > > -----Original Message----- > From: owner-informix-list [mailto:owner-informix-list@iiug.org] > Sent: vendredi 26 juin 1998 9:22 > To: informix-list > Subject: New Era Prblemette > > Is there an equivilent in New Era to SQL INTERRUPT ON? > So, as soon as an sql statement is executed, if I feel as though its > going > on for too long I can stop it part way? > Would I be able to create a button that the user can click, to interrupt > a > select??? > > Any advice welcome > > Jamie >