|
I wouldn't suggest hard coding the password or user id into your RPG program. You should use a data area as Booth suggested or create a file that holds user authority information for menu options, programs, fields, etc. You could use the file in future applications. Mike Troxclaire wrote:
Frank, Thanks for the input. In our shop lots of users have access to that menu option and we want only one user to have the authority to enter the
'Ending
Mileage'. That is the reason why we want the field to be password
protected.
I think I will go with the suggestion of having a password field by the
side
of the 'Ending Mileage' field. When the user submits the data I just have
to
do a check on the password supplied in my RPG program, right? Seems easy enough, any gotcha's? I appreciate your suggestion. Mike.
As an Amazon Associate we earn from qualifying purchases.
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.