Note also that you need to FETCH NEXT to visit every row in the cursor; your
code only did a FETCH.

Note further that Brian Freeman suggested an alternative solution which
avoids the cursor altogether.  You should heed his advice, as his solution
would probably be an order of magnitude faster and way less of a burden on
the server...

Cursors are evil ... ;-)

--
Jeff Mason              Custom Apps, Inc.
Jeff@c...


-----Original Message-----
From: alan.edwards@n... [mailto:alan.edwards@n...]
Sent: Monday, November 04, 2002 5:33 PM
To: sql language
Subject: [sql_language] Re: Whats up with this cursor?


What a balloon, you are right Dan, I havent opened the cursor! I somehow
completely missed that, thanks very much!