I think you could develop iSeries (server-side) stored procedures to
access or update only those selected files, and change your VB front-end
to CALL the stored procedure via ODBC.
The stored procedure *PGM can adopt owner authority so it has access to
those files. Give the program *PUBLIC *EXCLUDE and grant authority to
*USE the program only to those users who are authorized to run this VB
front-end client/server application to update those files. These stored
procedures could also be designed to take care of any commitment control
issues (somehow know when to issue a COMMIT).
That way, users cannot access or update those files directly through
ODBC (e.g. via Excel).
Regards,
Mark S. Waterbury
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
