Frequently Asked Questions
Security
- How do I modify the desktop shortcut to
receive a logon prompt when opening the database?
- What is the default user name and
password?
- How do I add new users to my database?
- How do I restrict user access to
menus, forms, and reports?
The default desktop shortcut created during
installation does not open the database with a logon prompt. To
enable user-level security and prompt users with a login screen when
they open the database, the shortcut used to open the database needs
to be modified as follows:
- Locate and select the Catalyst MFG
desktop shortcut created during installation.
- Right-click the shortcut and select
the Properties option from the shortcut menu.
- To add a workgroup switch, move to the
end of the Target field, type a space, and include
the following text:
/WRKGRP "C:\Program
Files\Catalyst\Catalyst.mdw"
If you want users to login with their user name, move the
workgroup file to a shared network folder and modify the
directory path accordingly. Please refer to the help topic,
Enabling User-Level Security, for more information.
- To activate the logon screen, the target
path must also include the path and file name of the Microsoft
Access application (MSACCESS.EXE). The Access path will vary
depending on the Microsoft Office version or Access Runtime
installed on the machine. In most situations the file can be
found under the Program Files\Microsoft Office\Office folder.
The location can be verified using the “Find Target…” button. An
example target path for Access 2000 is listed below. For Access
XP, use Office10\MSACCESS.EXE. For Access 2003, use
Office11\MSACCESS.EXE, For Access 2007, use
Office12\MSAccess.EXE.
"C:\Program
Files\Microsoft Office\Office\MSACCESS.EXE"
An example target path that includes all three components
(Access path, file name path, and workgroup switch is listed
below.
"C:\Program
Files\Microsoft Office\Office\MSACCESS.EXE" “C:\Program
Files\Catalyst\Catalyst v4.xx.mdb” /WRKGRP "C:\Program
Files\Catalyst\Catalyst.mdw"
- To provide a default user name at login
using the Windows user name, you can add a user switch as
follows:
/user %username%
-
Click OK on the Properties window to save the new
shortcut properties.
What is the default user name and password?
The default user name is sysadmin and the password is blank.
After adding new users, the sysadmin password should be changed
to restrict to administrative use only. The sysadmin user should
never be deleted. To require a logon password, set the 'Require
Logon Password' flag on the System page of the Company Master.
Please refer to the 'Enable User Level Security' help topic for
more details on creating user names and passwords.
How do I add new users to my database?
To create a new user name to login to Catalyst,
perform the following steps:
-
Select File > Security Maintenance >
User and Group Accounts from the Catalyst menu.
-
Click on the New button in the
User pane. On the 'New User/Group' screen, enter the desired
user Name and Personal ID. The user name
should match the Windows user name if you want it to default
when the user opens the database. The Personal ID is used to
create a permanent security ID for the user. Keep a record
of the personal ID you enter for each user in case you ever
need to recreate your workgroup file.
-
Select OK to create the new
user.
How do I restrict user access to menus, forms,
and reports?
You can establish Object-Level Security in
Catalyst to setup permission levels for selected forms, reports,
and menu options at the user group level. Combined with user
name and group accounts, object-level security provides a means
to limit access to program functionality and control what users
can view or change down to the field level.
Before applying object-level security, it is recommended that
you establish user groups to represent the functional areas or
departments within your company. Please refer to the Create New
User Group and Assign User to Groups help topics for more
information. After the desired functional user groups have been
established, you can proceed with establishing object-level
security. Please refer to the Object-Level Security help topic
for more details.
| 
