prepare,declare,open ADDITIONAL HELP REQUEST

This is an update and additional request for help on previously mentioned problem. I have a LARGE program where one module has a number of select statements that are implemented using this method. . . A. create temp table . . . create index . . . prepare "sql statement that joins permanent table with temp table" . . repeat A for multiple tables and selects drop temp table . . . B. create temp table . . . build temp table . . . create index . . . C. declare open while true D. fetch end while . . repeat C for multiple tables and selects E. drop temp table get new data go to B 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. Program NOW returns STATUS = 100 on the first execution of the fetch, on at least TWO Fetch statements, as in "D" above. Where it did not before. There may be others that I have not been able to test yet. Basically it is acting as if the temp and permanent tables are empty or the joins are not finding anything. * As a debug procedure I added select statements in front of these fetches and THEY WORKED FINE. * As a debug procedure I duplicated suspect code into a small test program and it WORKED FINE. Something "broke the bank" as it were. 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? Could it be out of string space or prepare "ID" space? Any insight in to how to approach this problem would be helpful. -- Michael J. Kuhn Computer Systems Consultant phone:410-254-7060 Email: mkuhn@csd.clark.net, csd@clark.net mkuhn@rhlab.com c/o Baltimore Rh Typing Laboratory, Inc. phone:410-225-9595