 | |
#1
 
| |||
| |||
|
RESULTSET LIMITED TO 1048 -
08-26-2004
, 05:09 PM
#2
| |||
| |||
|
|
"Theresa Casagrandi" <hr (AT) webzooks (DOT) ca> wrote in message news:LCtXc.120$is1.2994 (AT) news20 (DOT) bellglobal.com... I've setup Stored Procedures in an Oracle 9i DB and am calling them from ASP into an ADO Recordset. The calling parameters specify a Resultset of 1048 to be returned. The OUT paramaters have been set up and a cursor is used to loop through and populate the each result set record. Everything works fine provided that result set does not return more than 1048 records. If I attempt to set Resultset paramater to any more than 1048 a cryptic error occurs. What this of course means is that I can't retrieve any more than 1048 records without a fatal error. Anybody know what's going on here? Were using an ODBC Oracle drive under IIS5, with ASP and ADO. Thanks Why not just pass the result set directly via the out parameter and let the application determine how many rows it wants to fetch? The application gets the out parameter and does a fetch on the cursor. Jim |
#3
| |||
| |||
|
|
I've setup Stored Procedures in an Oracle 9i DB and am calling them from ASP into an ADO Recordset. The calling parameters specify a Resultset of 1048 to be returned. The OUT paramaters have been set up and a cursor is used to loop through and populate the each result set record. Everything works fine provided that result set does not return more than 1048 records. If I attempt to set Resultset paramater to any more than 1048 a cryptic error occurs. What this of course means is that I can't retrieve any more than 1048 records without a fatal error. Anybody know what's going on here? Were using an ODBC Oracle drive under IIS5, with ASP and ADO. Thanks Why not just pass the result set directly via the out parameter and let the |
the out parameter and does a fetch on the cursor.
Jim
#4
| |||
| |||
|
|
The fatal error occurs within the stored procedure as a result set is being populated. Everything is ok up to 1048 and then on the next record........., a fatal error occurs. Thanks for responding and offering some thought to the problem. .. "Jim Kennedy" <kennedy-downwithspammersfamily (AT) attbi (DOT) net> wrote in message news:gPvXc.188607$8_6.102059 (AT) attbi_s04 (DOT) .. "Theresa Casagrandi" <hr (AT) webzooks (DOT) ca> wrote in message news:LCtXc.120$is1.2994 (AT) news20 (DOT) bellglobal.com... I've setup Stored Procedures in an Oracle 9i DB and am calling them from ASP into an ADO Recordset. The calling parameters specify a Resultset of 1048 to be returned. The OUT paramaters have been set up and a cursor is used to loop through and populate the each result set record. Everything works fine provided that result set does not return more than 1048 records. If I attempt to set Resultset paramater to any more than 1048 a cryptic error occurs. What this of course means is that I can't retrieve any more than 1048 records without a fatal error. Anybody know what's going on here? Were using an ODBC Oracle drive under IIS5, with ASP and ADO. Thanks Why not just pass the result set directly via the out parameter and let the application determine how many rows it wants to fetch? The application gets the out parameter and does a fetch on the cursor. Jim Not seeing the code it is rather difficult to comment on the error in the |
there?
Jim
#5
| |||
| |||
|
|
"Theresa Casagrandi" <hr (AT) webzooks (DOT) ca> wrote in message news:L5wXc.30407$DG.1428992 (AT) news20 (DOT) bellglobal.com... The fatal error occurs within the stored procedure as a result set is being populated. Everything is ok up to 1048 and then on the next record........., a fatal error occurs. Thanks for responding and offering some thought to the problem. .. "Jim Kennedy" <kennedy-downwithspammersfamily (AT) attbi (DOT) net> wrote in message news:gPvXc.188607$8_6.102059 (AT) attbi_s04 (DOT) .. "Theresa Casagrandi" <hr (AT) webzooks (DOT) ca> wrote in message news:LCtXc.120$is1.2994 (AT) news20 (DOT) bellglobal.com... I've setup Stored Procedures in an Oracle 9i DB and am calling them from ASP into an ADO Recordset. The calling parameters specify a Resultset of 1048 to be returned. The OUT paramaters have been set up and a cursor is used to loop through and populate the each result set record. Everything works fine provided that result set does not return more than 1048 records. If I attempt to set Resultset paramater to any more than 1048 a cryptic error occurs. What this of course means is that I can't retrieve any more than 1048 records without a fatal error. Anybody know what's going on here? Were using an ODBC Oracle drive under IIS5, with ASP and ADO. Thanks Why not just pass the result set directly via the out parameter and let the application determine how many rows it wants to fetch? The application gets the out parameter and does a fetch on the cursor. Jim Not seeing the code it is rather difficult to comment on the error in the code. How about in sqlplus, do you get an error running the stored procedure there? Jim |
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.