Re: 4GL Version 6.x : Bugs, or just worms?

In <5dchtg$b73@gulfa.kuwait.net>, Rudy Fernandes wrote: }We have recently upgraded from 5.0SE to 7.2 ONLINE and RDS 4.1 to 6.04. } }1. We are having problems with the 'SKIP TO TOP OF PAGE' statementunder }some conditions. } }Most of our reports have a FIRST PAGE HEADER. To prevent data from }being printing on the first page, we have statements like these } }ON EVERY ROW (or BEFORE GROUP OF ...) } IF PAGENO = 1 THEN } SKIP TO TOP OF PAGE } END } }Informix fails to execute the SKIP TO TOP OF PAGE under 6.04. After }much perspiration, we discovered that the following works. } }ON EVERY ROW } IF PAGENO = 1 THEN } SKIP 1 LINE } SKIP TO TOP OF PAGE } END IF } }What's going on? } }2. VARCHAR. In our ongoing effort to improve the performance of our }ONLINE engine, we decided to switch a set of columns from CHAR to }VARCHAR (more rows per page, etc). } }Following this, we were shocked to find that SELECTs on that column } returned NOTFOUND. We quickly discovered that the problem occurred } if the variable being used in the select was defined as LIKE } tabname.VARCHARcol. If we changed the variable to a CHAR, it worked } fine. } }Can anybody shed some light on this extraordinary behaviour? } }TIA. } }---------------------- }Rudy Fernandes }GIC, Kuwait }---------------------- Rudy, 1.) What you told about reports are correct, I4GL has become smarter, insted of counting total lines in the phycal/hardcopy page, it now counts the lines after the header, excluding whatever you have printed in the header. If your reports are printing, their selection criteria, or stuff like that, in the first page header and jumps to top of next page, in every first row using pageno, as you have mentioned, you need to do a skip / print. 2.) We have a lot of columns with varchar type, we haven't experienced the 'NOTFOUND' problem, that you mentioned. In fact we don't have any problem in selecting varchar column alone or the whole record, using only varchar column in where clause or any other column. There could be sothing else going wrong. Otherwise I am not understanding the problem, in which case I will appreciate if you can explain it in detail. Felix K. Mathews DHL Systems Inc.