|
Hello
Thomas!
As you mentioned I just had to use a cursor name in Capitals ($CURSOR
=
'LEOLEO_CURSOR' instead of 'leoleo_cursor') and now it's working
perfect.
Thanks a lot!!
(Gerald)
----- Original Message -----
Sent: Tuesday, March 18, 2003 6:05
PM
Subject: RE: ODBC / ADO: can dbprocs with
cursors as result be used now?
Hi Gerald
> -----Original Message-----
> From:
Gerald Nowitzky [mailto:[EMAIL PROTECTED]
> Sent: Dienstag, 18. M�rz
2003 16:08
> To: [EMAIL PROTECTED]
>
Subject: ODBC / ADO: can dbprocs with cursors as result be used now?
>
>
> Sorry for asking again; this time more detailed:
>
> I have defined this dbproc:
>
> CREATE DBPROC
LEOLEO
> RETURNS CURSOR AS $CURSOR = 'leoleo_cursor';
> DECLARE
:$CURSOR CURSOR FOR SELECT * FROM DBA.USERS;
>
> The Table
DBA.USERS contains some Data.
> - When I execute
>
> CALL
LEOLEO
>
> in SQL-Studio, I just get "Statement successfully
executed. No Result"
So far I know, SQLStudio does not support this
feature yet.
>
> if I am defining an ADO Recordset and do the
CALL there:
>
> Set objRS =
Server.CreateObject("ADODB.Recordset")
> objRS.Open "CALL
LEOLEO",adOpenStatic,adLockReadOnly
>
> I get an Error: "ADODB
Recordset: Arguments are of teh wrong
> type, are out
> of
acceptable range, or are in conflict with one another"
I remember that
within importing a dbproc into ADO, you have to
set in the properties
dialog, tab advanced the flag
"Recordset Returning".
But this may differ
from the way you call dbprocs.
As long as I write the cursor name
in small letters, I get
the same error as you (second mail, -4000) but
following works:
CREATE DBPROC LEOLEO RETURNS CURSOR AS $CURSOR =
'LEOLEO_CURSOR';
DECLARE :$CURSOR CURSOR FOR SELECT * FROM
domain.users;
HTH
Thomas
----------------------------------------------
Dr. Thomas
K�tter
SAP DB, SAP Labs Berlin
SAP DB is open source. Get
it! www.sapdb.org
_______________________________________________
sapdb.general
mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
|
