My company is currently in the process of porting an
Microsoft Access client/server application using Sybase as
the back-end server to an app which will use Oracle as the
backend database engine.
In Sybase, stored procedures have the ability of returning
records. For example, after "Create procedure Foo as Select
* from ATable" is run, this stored procedure in Sybase
returns all rows from ATable in an Access Pass-Through
query which simply has "Foo" in its body. Now, in Oracle,
it appears one must have a "SELECT INTO" statement in
procedure creation calls rather than plain "SELECT"
statements which return rows. The ORACLE case seems to
demand management of temporary tables which store "Select
into" results which somehow then have to be found and
managed by the client Access application. There seems to be
a huge overhead associated with this process.
Does anyone know of a workaround to avoid all this
appearant need for table management? Are there ways of
making stored procedures or functions (or other techniques)
in ORACLE return records bypassing the need for server temp
tables (and all the necessary overhead)?
Thank you.
Stefan.
Stefan Wallgren -- wallgren_at_mcgi.com --voice 415.491.1770
--fax 415.491.1251 --
