Hi
Is it possible to use NonBlocking with a TOraStoredProc component?
If I setup and activate my TOraStoredProc with NonBlocking = True, I get an exception stating "SQL statement doesn't return rows". If I set NonBlocking = False, and activate the Stored Proc, it works fine. This happens both at design time and runtime.
Do I need to handle any event or set any other property to operate this?
Thanks
NonBlocking and TOraStoredProc
Re: NonBlocking and TOraStoredProc
Hello,
Thank you for the information.
We have already fixed the problem.
This fix will be included in the next build.
The next build will be released in one or two weeks.
Thank you for the information.
We have already fixed the problem.
This fix will be included in the next build.
The next build will be released in one or two weeks.
Re: NonBlocking and TOraStoredProc
ok. Thanks.
As a paid subscriber to the Professional version with source, is there any chance I can get an update earlier or are you able to provide the fix so I can implement it until such time as it's resolved? Assuming it's not too complicated.
Thanks
As a paid subscriber to the Professional version with source, is there any chance I can get an update earlier or are you able to provide the fix so I can implement it until such time as it's resolved? Assuming it's not too complicated.
Thanks
Re: NonBlocking and TOraStoredProc
hello,
To fix this problem, you should replace the following code in the OraClasses.pas module, in the TOCIRecordSet.DoExecFetch; method
with
To fix this problem, you should replace the following code in the OraClasses.pas module, in the TOCIRecordSet.DoExecFetch; method
Code: Select all
if not FDisableInitFields then begin
InitFields;
end;Code: Select all
if not FDisableInitFields then
InitFields
else
InitFetchCursor;Re: NonBlocking and TOraStoredProc
Thanks.
Seems to work perfectly.
Seems to work perfectly.
Re: NonBlocking and TOraStoredProc
Hello,
Glad to see that the problem was solved. If you have any other questions, feel free to contact us.
Glad to see that the problem was solved. If you have any other questions, feel free to contact us.