Re: OnLine not setting cisam code

In an earlier posint this week, I stated that OnLine was not setting the cisam code in a particular case. This is not true; OnLine IS setting the cisam code. What our application found was an implementation difference between Turbo and OnLine: Under Turbo, a $close cursor operation does not reset sqlca.sqlerrd[1] (the cisam code). Our database interface routine closes the cursor upon detecting an sql error, and the calling routine inspects the cisam code, which turned out to be for the operation that failed. Under OnLine, the $close cursor operation sets the cisam code. Our calling routine, therefore, saw a 0 cisam code from the close operation, and not from the failed operation.