On 5/10/2023 9:37 AM, Greg Wilburn wrote:
Yes, so the whole point is not having to explicitly specify each column on the insert from ICPRTMIA to AUDIA

ICPRTMIA AUDIA
IACOM# IACOM#
IAPRT# IAPRT#
IA101 IA101
etc... etc..
IAUSRN
IAUSER
IATRND
IATRT
IAPRCF IAPRCF
IAVIAC IAVIAC
IAHCD1 IAHCD1
<end> <end>


The suggestion of a stored procedure was just to abstract and externalise the action/process of creating an audit record. Putting the code in a sub-procedure in a service program is an excellent way to do this. One can use native I/O in a sub-procedure; SQL is not a technical requirement.

I have cobbled together a Python program that creates a text file of column names. I pasted it into https://code.midrange.com/b4b44fc1d8.html
It saves me a bit of typing, and perhaps it will save someone else some time as well.
--buck



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.