<esc><esc> required w/ Perform Forms
User reported that Perform Forms on ISQL 7.20.UD1 for Linux required two escape characters to start a query on subsequent attempts after the first query (which needed only one). A respondent confirmed this as a known bug in Perform and mentioned a patch was being developed, but no specific fix or workaround was provided in the thread. One suggestion was to reassign the ACCEPT event to a different key like F12.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Does anyone have any advice on how to correct a problem where two <escape> characters must be sent to start a query from a Perform form? It works fine the first time with just one <esc>, but takes <esc><esc> on subsequent queries. ISQL 7.20.UD1 on Linux-221. -- Daryl Jones daryl@tcomeng.com Telecommunications Engineering Associates Voice: (650) 596-1100 Ext. 201 San Carlos, California http://www.tcomeng.com/
Try to move ACCEPT event to another key (for example to F12) Daryl Jones <daryl@tcomeng.com> wrote in article <7cv77n$in4$1@net2.smrn.com>... > Does anyone have any advice on how to correct a problem where two > <escape> characters must be sent to start a query from a Perform > form? It works fine the first time with just one <esc>, but > takes <esc><esc> on subsequent queries.
it sounds like a terminal emulation problem to me. it seems that what's displayed after your first query somehow 'traps' the first escape sequence. would you have any control characters (not visible) in your records? try to make sure that that's not the case 'cause you will have problems more problems with those in the future... K
I also have the same problem = I know it's application-related as I just dbimported the database and recompiled the code from another platform where every-thing is fine. Not sure what to make of it, but it's a definite problem.... -Rick Mills Kgoozis <kgoozis@aol.com> wrote: > it sounds like a terminal emulation problem to me. it seems that what's > displayed after your first query somehow 'traps' the first escape sequence. > would you have any control characters (not visible) in your records? > try to make sure that that's not the case 'cause you will have problems more > problems with those in the future... > K
Daryl Jones wrote: > > Does anyone have any advice on how to correct a problem where two > <escape> characters must be sent to start a query from a Perform > form? It works fine the first time with just one <esc>, but > takes <esc><esc> on subsequent queries. > > ISQL 7.20.UD1 on Linux-221. > > -- > Daryl Jones daryl@tcomeng.com > Telecommunications Engineering Associates Voice: (650) 596-1100 Ext. 201 > San Carlos, California http://www.tcomeng.com/ There is a known bug causing this. don't know if patch is available or not yet.
Rick Mills wrote: > > I also have the same problem = I know it's application-related as I just > dbimported the database and recompiled the code from another platform > where every-thing is fine. Not sure what to make of it, but it's a > definite problem.... > There is a known bug causing this. they are working on a patch. Paul