Frank

        Why not place an account password on the account you are updating.
        That would keep those that use it out, while the other accounts would
        be unaffected. Just remember to remove it when done.

Bob Schlosser
(321) 674-4938


-----Original Message-----
From: Girard, Frank [mailto:[log in to unmask]]
Sent: Friday, January 28, 2000 11:54 AM
To: [log in to unmask]
Subject: Restricting user logon by account rather than system wide.


We are looking for a way to restrict user access by account, rather than
globally using limit 1,1.  Telling the users about hipri is not an options
as this defeats the purpose, as well as being a security issue.  I am
looking to restrict all users except 1, the manager of the account.

We are fast coming up on a situation where we need to apply updates to an
account, but in the update instructions it has us set the limits to 1,1.
This cause all the users to get kicked out when they try to log onto an
account that is not involved in an update.  Here is the information:

We are running MACS from Smith Gardner, this is a MAil order and Catalog
Supply software package.  This software is set up in 3 major accounts, 1
account for each company that uses it.  The companies / accounts are WNG, BT
and MP4.  The problem is that while I am applying an update to WNG, with the
limits set to 1,1, the order processors who are logging into BT and MP4
can't log in because the limits are set to 1.1 even though the update does
not involve them.  Here's another example, WNG is doing a month and a year
close this Saturday.  We are testing in BT and MP4.  The limits are set to
1.1 we cannot do any testing in these accounts, even though nothing in
theses accounts affects WNG.

Thanks in advance for your input and help.

Frank Girard
[log in to unmask]
781-828-9300 X2738