Brad,

Add a column to that table for the userID who added the row, then use a before insert trigger to update that userID on insert, and to validate it via a before update or before delete trigger, and reject the transaction if it does not match the desired userID.

Mark


On Wednesday, August 24, 2022 at 11:29:57 AM EDT, Brad Stone <bvstone@xxxxxxxxx> wrote:

Is there anything out there/built in where you can set up record level
security to a DB so only a user who wrote the original record can
access/read/change the record in the file?

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any Cloud
Provider!

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.