Please post the syntax of the overlaid Indicator array!
There are multiple ways to define it.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
-----Ursprüngliche Nachricht-----
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
dlclark@xxxxxxxxxxxxxxxx
Gesendet: Thursday, 17.11 2016 17:06
An: Midrange Systems Technical Discussion
Betreff: Re: SQL Indicator Arrays
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 11/16/2016
11:15:45 AM:
I find that I have to have an SQL indicator array that is
overlaid
with a matching data structure so that I can have both named
indicators and subscripted indicators. Anybody else find that to be
true? I find that I need both because the SQL precompiler will not
iterate an
indicator
data structure but will also not allow the use of subscripts from the
indicator array. For example... The following is not allowed:
...snip...
On the flip side, it is a nuisance (to me) to have to manually
create and maintain such a data structure. So, has anybody come up
with
a
means of automatically generating an SQL indicator array with an
overlaid
data structure that matches the RPG-generated data structure for an
external SQL view reference? If not, maybe it is time for an RFE?
...snip...
Thoughts? Reactions? Thanks.
Neither thoughts nor reactions from anyone, eh?
Sincerely,
Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
****************************************************************************
*****************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please immediately
notify the sender and delete and destroy the message and all copies. All
unauthorized direct or indirect use or disclosure of this message is
strictly prohibited. No right to confidentiality or privilege is waived or
lost by any error in transmission.
****************************************************************************
*****************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
