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 firstname.lastname@example.org.
And to Charles WItt, I and used to make a practice of it every time,
listing out the fields, the entire record format, since that way it
doesn't depend on the fixed record format and you don't have to
recompile for changes to the format. This shop has no identity fields,
and not much SQL going on. Just two of us are sort of well-versed with
it, use it a lot, and another few do basic stuff like input one-record
at a time cursors, not much else.I gave a talk on the glories and how-to
of multi-row fetch, but the shop is stable (longevity) and got such a
late start getting with all the cool stuff that there's all this
technical debt and so they're actually going to migrate off of "RPG".
There goes another one.. But I'm at my twilight years, and the world has
gone crazy, so we'll see what happens...
In this case, this file is has so many fields, and the changes I'm doing
for this project are sorely needed by the team that uses it, I wanted to
get it done fast. They have a performance hit of waiting an average of
literally /*five minutes!*/ (I've clocked it) to get from the menu
option to the first subfile screen when they start! Ouch! And they're
used to it! So I'm in a hurry. But that "UPDATE QTEMP.TABLE2 SET ROW =
:</data structure/>" is something new for me, so I'm glad I asked.
(And I was curious about was there a way to do it that way,
Thanks everybody! Have a great week!
On 7/19/2022 9:39 AM, Rob Berendt wrote:
You may want to rethink that. Suppose you add derived columns, or those which have default values. Examples include some of the timestamp, job user, etc columns used for temporal tables. Do you really want to manually override these? IDK if making these columns implicitly hidden would remove them from appearing in the data structure.
But if you're sure you want to do that then google is your friend
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2023 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.