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



More or less all relational databases support transactions and commit
logic, precisely to handle the multiple user issue you are talking
about. That's one of the draws, perhaps the main one, of using a
relational database for enterprise applications.

And since your question is about using this *in RPG* it is actually
most suited for that list. Especially since RPG has some opcodes
specifically for that, which aren't in most languages. With most other
languages, this would be an SQL question (which you could also use in
RPG).

John Y.


On Thu, Jan 13, 2022 at 12:32 PM <smith5646midrange@xxxxxxxxx> wrote:

I have a header table and a detail table. The header table has an auto
increment field for its key that is used to join the detail table. If I
have multiple users updating the header table at the same time, how do I
know the value on the header record that was just inserted so it can used
when inserting the detail records? I have been googling and it looks like
the only way to find it is to use transactions and commit logic (and maybe
the method I'm finding only works on MySQL and other non-DB2 platforms). Is
there a way other than using transactions and commit logic?

While the program that I am writing is RPG and I considered posting this to
that forum, I'm asking this in the technical forum because I assume other
high level languages have the same problem (like windows programs using ODBC
connections).

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.