Re: Fixes to Informix 4gl

The worst problems I've had with Informix 4gl all involve bugs with the product. My version of 4.1 suffers from the "out of temporary string space" WORDWRAP and USING bug as well as a core dump on INPUT ARRAY bug, other WORDWRAP bugs, and a dbload bug. There are undoubtedly others, but I can't get a list of known bugs from Informix without upgrading my tech support. As soon as another product emerges that I hear good things about that is put out by a compnay that's less complacent with its customers, I'm definately going to try to switch. Until that happy day, let me report a new bug in Informix 4gl RDS 4.1: The CURRENT function, which I use to time reports called from a 4gl program, returns the wrong time in thousandths of seconds, occasionally causing reports which take less than a second to run to appear to have run in negative elapsed time. Here's what the CURRENT function will report if you call it repeatedly: Hours, minutes, seconds, thousandths: 12:31:26.010 12:31:26.050 12:31:26.070 etc 12:31:26.900 12:31:26.940 Check this line out --> 12:31:26.000 12:31:27.010 etc At the end of every second, the thousandths of a second counter rolls from .94 to .00 while the second counter doesn't change. That means that if you are timing something and it happens to end at the end of a second, CURRENT will report that it ended at the beginning of the second. If it started during that same second, then when you subtract its start time from its finsih time you will get a negative elapsed time. I have no idea whether there are other problems with CURRENT at the ends of more important time units such as seconds, minutes, etc.