× 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.



Joe

This could be because, as far as I know, the precompiler does not try to resolve everything that the actual compiler does - so it does not know values for some things. Now I'm very open to correction in this area - heh!

Vern

PS - Is HEH a TLA for "hope everything helps"?

At 01:25 PM 3/2/2008, you wrote:

One last note, in case anyone else finds this info useful now or at a later
time... Who knows, it might be me searching for this info years from now :)

Although dim(%elem(arrds)) is valid syntax, the SQL compiler will not allow
you to use an array defined that way in an SQL statement (SQL5011). The
same goes for dim(someConstant) syntax.

Only by hardcoding DIM(50) was I able to get past the SQL precompiler. I
only needed to hardcode the DIM(50) on the definition for the array that is
used in my Fetch Into SQL statement. All other likeds declarations use the
dim(%elem(arrds)) syntax. All seems to be working as desired now.

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.