|
> -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx / CWilt@xxxxxxxxxxxx > Sent: Friday, August 06, 2004 1:12 PM > > > Any thoughts as to how to prevent users from getting back > > in to certain programs/files? > > > > We need to implement something to lock out accounting stuff > > mostly during our end of month. Ending QINTER, isn't an > > option because other users can still be working. Two options (really, WAGs) come to mind: Put the accounting users in another interactive subsystem. -or- If there is a common menu or file that they have to go through to do their work, temporarily disable the authority to the objects they need to use. Don't know whether this will work immediately, or how it affects users already using such objects. hth, db
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.