Hi Mohammed,
Thank you very much. Procedure calls are working perfectly now. The error I was constantly making was using -1 as string parameter size. '-1' works for numbers but not for strings :-)
I need some more "little" help if you don't mind - I cannot get the result of a function call (called using ADODataSet or ADOStoredProc because ADOCommand doesn't recognise it as a SP). The call itself is successful. Is there any way (or workaround at least)? Additional 'hidden' parameter perhaps, or a returned dataset containing one value only? Alternatively I will ask PL/SQL developers to make procedures only, no problem at all.
I can also close this question at this point because you already helped me alot and open a new one later on about functions. Let me know what you think.
Thanks, Geo
Main Topics
Browse All Topics





by: mnasmanPosted on 2005-11-26 at 09:50:15ID: 15365319
Hello Geo,
ateParamet er('Str1', ftString,p dInput,100 ,'string1' ); ateParamet er('Str2', ftString,p dInput,100 ,'string2' ); ateParamet er('Str3', ftString,p dOutput,10 0,null);
You can do that with AdoCommand, then define the parameters, and read the output parameter value
I tested this with Delphi 7, Oracle 10G R2
var
P: TParameter;
begin
AdoCommand1.CommandText := 'GEOTEST.GeoConcatProc';
AdoCommand1.CommandType := cmdStoredProc;
adocommand1.Parameters.Cre
adocommand1.Parameters.Cre
P := adocommand1.Parameters.Cre
AdoCommand1.Execute();
ShowMessage(P.Value);
end;
HTH
Regards,
Mohammed Nasman