Re: sql weirdness...

[Yivi <nardus@xxxxxxxxx>]

After much mucking around, found the problem in a second piece of SQL code
that was nested inside the dow loop.
The program has a couple thousand lines, and the code in question was
supposedly checked by someone more knowledgeable than myself, so I tended to
put too much trust in it.
 Sorry about all the fuss, thx for all your help.
 Regards,
 I.-

 On 11/14/05, McGovern, Sean <Sean.McGovern@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> If you sign off and sign back on again the first call to the program
> should
> result in the cursor being opened and the rows being read from the cursor
> correctly. However, it appears that your code doesn't close the cursor
> once
> all rows have been read from the cursor. Subsequent calls to the program
> will therefore result in the cursor not being opened (as it is already
> open)
> and no rows from the cursor being read as the last row in the cursor has
> already been read.
>
> Ensure you close the cursor once all rows have been read. Alternatively,
> monitor for the cursor already being open and close and reopen if
> necessary.
>
>
>