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



On Tue, 9 May 2023 at 16:51, Greg Wilburn
<gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

I have two files/tables that are nearly identical. They are:

1. Part Master file
2. Part Master Audit file

The Audit file contains 5 additional fields that are not found in the Part Master. All of the other fields in the file are identical (mirror images of each other in name and attributes), and are in the same order EXCEPT for the last ten fields in the Audit file. The Audit file contains the 5 additional fields inserted just before the last 5 matching fields.

With RPG, I could simply chain (or read) the Part Master record, eval the 5 additional field values, and then just write the Part Master Audit record.
I'm looking for an "elegant" way to do the same thing with SQL without using native access. This will be running in a CGI job.

Any ideas?

I take it that you aren't keen on having to specify each column name
in the INSERT - twice. Me, either.

To me, this sounds like a stored procedure. Pass it the part num, and
under the covers the proc gathers the necessary audit information and
does the INSERT. The CGI program just does
CALLInsertPartMasterAudit(the_part_number); Or, just have the stored
proc run an RPG program of the style you might be accustomed. There's
a benefit to this: If you have a cross-reference tool, it'll be able
to see your source code and tell you where these part and audit files
are being used.

--buck

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.