Re: Stored Procedures

} Roy, } } This is a known bug between i4gl and Online 5.0 It is due to the fact that } 5.0 issues statement id for each stored procedure and statement in the stored } procedure. Theses numbers can get very high if you repeatedly call the } procedures. Unfortunately 4GL cannot hold numbers this high so it truncates } them effectively making the statement id in 4gl point at the wrong statement } in the engine. The next time you refer to the statement there is a mismatch } which results in fairly random error messages. } } Workarounds. This can be mostly worked around by declaring all stored procs } once at the beginning of the program. This way statement id's issued for the } stored procedures are all low enough to be recognised by 4GL. The above workaround should have read that all SQL statements in the 4gl program should be preapred and declared at the beginning of the program not just those cursors and execute statements which refer to the Stored procedures. Sorry - jim