×
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.
<snip>
If I only had to code for VRM540 and above I would probably drop the
prefix and use PREFIX to map file field names to qualified data
structures.
</snip>
Amen brother. We had a vendor package that even many releases ago would
use the same field name in all files. For example, if it was ITEMNBR then
it would be ITEMNBR in all files, not AAITEMNBR, BBITEMNBR, etc. Even
though all programs had to manually use I specs to rename the columns
(think RPG/400 not RPGLE). Now it's so easy with PREFIX and QUALIFIED
that there's no need to keep them all separate. Even ancient tools like
Query/400 support T01.ITEMNBR, T02.ITEMNBR.
And it sure makes it easy to find a field by using
SELECT SYSTEM_COLUMN_NAME, SYSTEM_TABLE_NAME, SYSTEM_TABLE_SCHEMA
FROM syscolumns
WHERE system_column_name='ITEMNBR'
Try that on your system.
ps: What's DDS? :-)
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
