Re: Inconsistency with SQL in ACS vs RPG

Daniel Gross <[email protected]>
Newsgroups gmane.comp.lang.as400.rpg
Message-ID <[email protected]>
As I have already written, it would be nice, to have one or two examples.

My typical development process today is - trying to implement as much as possible and reasonable in SQL using iACS-RSS - then copy/paste the SQL into the RPG source and replacing constants with host variables and what else. 

I never had a query/statement that didn't work as expected. What I had lately where some complex SQL queries, that I couldn't pack into a view. But I had never a problem with putting the statement into SQLRPGLE-

Regards,
Daniel


> Am 06.10.2025 um 17:39 schrieb [email protected]:
> 
> I do nearly all my development using SQL and use the same process as Richard (Testing SQL statements in ACS). I agree with Richard and have struggled with stupid differences, sometimes putting in calls to IBM for assistance.
> 
> Darryl Freinkel
> A4G
> 
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: [email protected]
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: [email protected]
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
> 
> Please contact [email protected] for any subscription related questions.
> 
-- 
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact [email protected] for any subscription related questions.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.