×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Dieter wrote:
... if local means local to a procedure, it doesn't make too much sense,
because a cursor is not stateless. To encapsulate a > cursor, put it to a
module with setXXX and getXXX procedures and write data Access modules.
Yes, local to a procedure, or "Subprocedure" as named in the RDP outline.
I'm in over my head, but I see legacy RLA as "not stateless", so
thought maybe I would not need to declare cursors uniquely
between subprocedures.
Now, I know this does not work, but am not sure why.
For example: can a service program successfully declare a cursor
having the same name as cursor declared in a module invoking that
service program?
How about a called stored proceedure?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.