Further thought, if your existing logic is fixated on this "table" table
then how hard would it be to normalize into individual tables and create a
logical that contains them all? I think DDS is hampered by the lack of
derived columns while SQL could easily create a view like so:
create view fooref as
select 'ADT' as pritblnum, pritblent, sectblnum, sectblent from ADT
union all
select 'XYZ' as pritblnum, pritblent, sectblnum, sectblent from XYZ
union all
...
But trying a traditional RPG chain against that view would be a real hoot.
I don't suppose you've externalized your I/O so that changing that I/O
routine to fit this would be a simple retrofit?
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.