|
We have an application that launches a VB app thru RUNRMTCMD. We have the setting to run as logged on user. Generally this is not a problem. Except on the days that people change their passwords. Our protocol is to signon to both the network and the AS/400 with your existing password, then using a menu option on the 400, change that password and ust Ctrl-Alt-Del to get to the windows button to change that password. The problem appears to be that the initial connection bewtween the 400 and the pc is made with the old password. When they try to launch the VB app, it uses the new password and dies (or vice versa). Currently, we have advised everyone on the day they change passwords to reboot before working. Is there something we are missing ? We can't have the users signon each time they launch the VB app as they are in and out of it hundreds of times in a day. Suggestions ? Thanks, Cyndi B. Boise, ID
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.