Re: prepare,declare,open ADDITIONAL HELP REQUEST
Posted in 1996
mkuhn@rhlab.UUCP (Michael Kuhn) wrote: [...big snip...] >On Feb 6 this code worked fine AS IT HAS for the LAST 2.5 years. >I used ISQL to change a permanent table that was involved in ONE of the >select statements. I made a minor unrelated change to something is this >module. Recomplied and relinked. One assumes that you have not recently upgraded any Informix products. >This suspect module has been under continued revision and maintenance since >its inception. It has been recompiled many, many, many, many times. This >is without a doubt the wierdest thing that I have every seen 4GL do. >Does anybody have any clues as to were to look for this problem? We had a problem with an early version of Informix (4.00.UC1 ?), whereby when the program exceeded 420 odd kb strange things started happening. We had to cut out functionality as an interim solution. This may not be related, but you could easily cut out some chunks of code to see whether the problem is related to code size. >Could it be out of string space or prepare "ID" space? You should get an error reporting this if it is a problem. >Any insight in to how to approach this problem would be helpful. Try recompiling without the recent changes. That will confirm whether the change has affected things. Similarly, try recompiling without the table change. Do you use the "LIKE changed_table.*" or "SELECT * FROM changed_table" constructs ? These are suspect if you make table changes, and the code should be thoroughly checked to ensure that it stills works correctly, and the .4go files should be removed to ensure recompilation. By the way, you will find that your prepared statements will not be optimised correctly, because they are done with empty temporary tables. Cheers, Brent Jackson. brent@hypercom.co.nz Phone : 64-9-3603593 Fax : 64-9-3602840