If you decide to use Windows NT security instead of AcuServer system security, your users will have whatever permissions the system administrator has set up for them.
If, on the other hand, you opt to implement AcuServer system security, it is essential that you establish the proper ownerships and permissions on the acuserve executable file, server configuration files, server access files, and existing data files and directories.
Setting ownerships and permissions requires Administrator privileges. This section lists some key considerations for performing this activity. For specific instructions, consult your operating system documentation.
Note that the AcuAccess and AcuAccess.vix files should be readable and writable by "Administrator" and "System," with no other access.
Windows NT and Windows 2000 control access to resources with Access Control Lists (ACLs). An ACL specifically grants access to a user or to a group. Privileges are additive. The user has the highest access given to his or her account and to any groups to which that user belongs. The exception is "No Access," which overrides any other privileges.
Permissions are set by the account that owns the file. To override permissions, a non-owner must have the "Take Ownership" privilege and must use it to take ownership of the file before setting permissions.
The group "Everyone" contains every account on the system. Using this group is a handy way to set privileges, but can be a risky way to deny them. If a file or directory has "No Access" for Everyone, it will be unusable until someone (such as the Administrator) takes ownership and resets the privileges.
If you experience a problem with file access, it can be helpful to give the users Full Control of the files and directories they need to use. After everything is working smoothly, reduce access to Read-Only if desired. However, be sure to test each program to make sure that everything continues to function as you expect with the reduced privileges.
The AcuAccess and AcuAccess.vix files should be readable and writable by "Administrator" and "System," with no other access.
More: