"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 12/16/2016 11:28:40 
AM:
Anyway, if this is the cause of your problem - it won't run this way
in the current release. If you don't need a response parameter, you 
could simply use dynamic SQL or a function as stated before.
        In this case I have gotten around the problem by eliminating the 
stored procedure call and just coding the SQL that was in the stored 
procedure.  The other platform wanted me to call a stored procedure so 
that they maintain control of what SQL is actually executed on their 
system.  But, since the stored procedure call wasn't working they had to 
let me use direct SQL statement access.  But, this will not be acceptable 
in other cases where we need additional business logic to control the 
process.  We don't want to be duplicating business logic in more than one 
place.  So, in the future, we will need cross-platform MS SQL stored 
procedure calls to work.  Thanks.
Sincerely,
Dave Clark
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.