Good News Everybody!
The new search engine is LIVE!
Please report any problems to david (at) midrange.com.
|
Jim Franz wrote: > What might be considered a best practices approach as to how a > SQL Server or VB access to AS400 data would store a user id/profile? > Some of this might be server applications throughout the day making > requests. > The server programmers want a profile to "use" to read data (and I > expect someday to update). We do have *public excluded from all files > and authority by auth lists. I want something other than a hardcoded > user id/pwd inside some text file on a windoze machine. It's not a problem unless you want it all hands-off. If there's someone attending the software, then it'll ask for the user id and password the first time it connects and after every IPL and shouldn't need to again. If it's a hands-off application, then you have a problem because you don't want to store the password anywhere, yet there's noone available to enter it. Bill
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.