MDAC 2.8 and cursor FETCH NEXT

it seems that starting with MDAC 2.8 the FETCH NEXT statement for cursors requires an INTO clause. otherwise an unspecified error is returned.
so it's not possible to scroll through the records anymore without storing the values of the fields into local variables?Can you post the error code/description ?|||the following code executes from a connection object without issues using ado 2.6 and 2.7:

DECLARE c8281 CURSOR FOR
SELECT * From Users WHERE ( Users.User_ID = 17 )
OPEN c8281
FETCH NEXT FROM c8281
UPDATE [Users] SET
User_Name = 'Unknown'
WHERE CURRENT OF c8281
CLOSE c8281
DEALLOCATE c8281

however, if I use ADO 2.8 it returns error code 80004005 (unspecified error) and native error = 0. furthermore, it actually executes at the database server.

I made it work without errors by modifying the code in the following way:

DECLARE @.username VARCHAR
DECLARE c8281 CURSOR FOR
SELECT User_Name From Users WHERE ( Users.User_ID = 17 )
OPEN c8281
FETCH NEXT FROM c8281 INTO @.username
UPDATE [Users] SET
User_Name = 'Unknown'
WHERE CURRENT OF c8281
CLOSE c8281
DEALLOCATE c8281

which is closer to ansi92 I guess. but I just really need to scroll through the cursor. no need for local variables.

maximum limit on results

Is there a maximum limit on results returned? I didn't think so, but I'm
seeing only ~3000 rows of a 100,000+ row table in my report.Sorry, answered my own question. I was confusing pages and # of results.
Still, is there an upper limit? I cannot find any other documentation
besides 4 MB is an upper limit on report size.|||There is no limit on the number of rows per dataset or on the number of
datasets per report. However, you should consider that datasets with many
rows will need more processing time and reports with complex layouts and
many pages more rendering time.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andy S." <andymcdba1@.nospam.yahoo.com> wrote in message
news:%239t$dUcwEHA.1308@.TK2MSFTNGP09.phx.gbl...
> Sorry, answered my own question. I was confusing pages and # of results.
> Still, is there an upper limit? I cannot find any other documentation
> besides 4 MB is an upper limit on report size.
>