Re: About CONSTRUCT in R4GL and C4GL

Nils Myklebust <Nils.Myklebust@idg.no> wrote: >"Kevin Hu" <hugw@usa.net> wrote: >:I program with the Informix-4GL now. When I use the CONSTRUCT sentence >:in an opened window, when press interrupt key such as ^C, in R4GL it will >:work well but in C4GL you will get a error of "Forms statement error >:number -1145". Is there any other way to avoid this error? >On my machine finderr 1145 says (4GL ver 6.x): > -1145 Cannot open ERROR window. >and finderr 1319 says: > -1319 The 4GL program has run out of runtime data space memory. >I haven't ever run into this type of error in 4GL on Unix. May be you >have a very old version or some old strange C compiler? I think that this is a bug which got fixed two or three years ago; I recall something rather similar being fixed, if not the same problem. You can also get peculiar effects if you go closing the current form while the input statement is still active, and other similar operations. >You might of course want to try what the 1319 error states you should do, >but some newer versions might also help you out. Time for the periodic reminder to readers: ************************************************************* ** Include platform and product version number information ** ************************************************************* When you ask a question, please indicate which Informix product you are using (sometimes that'll be both an engine (OnLine or SE or IUS) and a tool (I4GL, ISQL, NewEra, ESQL/C, ...), and the machine you are using, with version numbers for both the Informix products and the o/s. Eg: I might say that I've tested something on Sun Sparc 20 running Solaris 2.5.1 with ESQL/C 7.23.UC1 and OnLine 7.23.UC1 and it {worked|failed}. In the absence of detailed version number information, I'd diagnose that Kevin is using a version of I4GL prior to 4.15/6.03, and that the best way to get that bug fixed is to upgrade. One other simple rule of thumb: if I4GL and I4GL-RDS behave differently and it is neither to do with uninitialized variables nor array subscript bound checking, then there is a very high probability that you've found a bug in one or the other of the products (and possibly both). They are supposed to work the same. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> PS: Warning I do not reply to messages with anti-spam in the return path.