Re: Problem using the declare cursor

[Michael Young]

Hi Ben,

Here is a copy of an email I sent to RBTI in May of 2001 during the beta testing. I had forgotten about it until I saw your post. Maybe it applies to your problem. I never heard back from them and so I never followed up on it.

----------------
I have not had time to thoroughly figure this out but I thought I might give you a heads up in case it rings a bell with someone else having problems. If I run 2 cursors (these are not nested cursors) back to back and the first cursor finds no rows, the second cursor gives me weird errors. This code runs fine in the latest release versions of both Windows and DOS and nothing has changed. The first error I got was that the second cursor had a BAD ORDER BY. This was definitely not the case. I found if I changed the variables in the where clause to actual values then it seemed to run fine. If I only had one condition in the where clause, even if it used a variable, then it also ran fine.

All my testing has brought me to the point that the first declare cursor coming
up empty causes the problem. If you need further information, then I will try
and build up a routine to demonstrate it. I have already spent about 4 hours
getting to where I am at and I need to go to a clients right now so just let me
know if you need assistance.
-----------------

Best regards,
Mike Young


--Original Message Text---
From: Ben Strickland
Date: Thu, 15 Nov 2001 20:28:12 -0800

Has anyone had experience with two files running one after another and both files use the Declare Cursor and for some reason I have to run the second file twice to get the Declare Cursor and other commands in the file to work. Any answers?
 
Ben Strickland