Re: RPG Cross-Platform to SQL Server -- RPG400-L

Subject: Re: RPG Cross-Platform to SQL Server
From: dlclark@xxxxxxxxxxxxxxxx
Date: Fri, 16 Dec 2016 10:52:52 -0500
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 12/16/2016 02:37:40
AM:

Stored procedure support was made for a customer, who needed it for

Oracle.

The diffrence between Oracle and MS SQL is, that MS SQL doesn't support
inout parameters (and at the moment ArdGate expects all parameters to be

inout).

It is true that MS SQL Server doesn't support the INOUT keyword,
but a stored procedure parameter declared with the OUTPUT keyword can
still be used as an INPUT parameter by default. We have already proved
this here that this works. So, I don't know why either ARDGATE or the
SourceForge MS driver would have a problem calling a MS SQL stored
procedure with one parameter which is both input and output capable.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: RPG Cross-Platform to SQL Server , dlclark

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.