What the system requirements for Catalyst?

The system requirements for Catalyst Manufacturing® are similar to those for Microsoft Access®.  Catalyst is split into a front-end database that resides on the client PC and a back-end database that resides on the server machine. The system requirements for each are provided below.

Client PC

• Computer: Most processing occurs on the client, so higher processing speeds and multiple processors will improve performance. A PC with at least a 1 GHz processor is recommended.
• Memory: 2 GB RAM or higher
• Operating System: Microsoft Windows® XP, Vista, or Windows 7.
• Software: Microsoft Access® 2000, 2002, 2003, or Access 2007. The Access Runtime version can be used on machines without an Access license. Microsoft Word® and Excel® are required for extended reporting and analysis. Microsoft Outlook® and Internet Explorer® or a comparable email client and browser are helpful for sending receiving data. The installation of the latest Office® service packs is recommended.
• Hard Drive: 200 MB of hard disk drive storage for both Microsoft Access® and the Catalyst application files on the client PCs.

Server

• Computer: A personal computer can be used when using Catalyst with a Microsoft Access® back-end database. When using the SQL Server® back-end database, a server rated machine is recommended, but not required since most processing occurs on the client. A server machine may be desirable, however, to improve data storage and backup capabilities.
• Operating System: Same as client OS or Windows Server 2000, 2003, or 2008.
• Software: A Microsoft Access® installation is recommended on the server when using an Access back-end database to perform database administration functions. When using a SQL Server® back-end database, the SQL Server client tools or equivalent third-party software is recommended to perform database administration functions.
• Hard Drive: At least 2 GB for company back-end database file.

Back to Top

How do I install Catalyst?

Since Catalyst is based in Microsoft Access®, each client machine must either have a licensed copy of Access or the runtime version installed on each client machine.  For network environments, the back-end database must also be placed on a server machine so it can be shared by all users.

Client Installation

1. Backup any Catalyst database files you may have in the Catalyst folder from a previous installation. Uninstall any previous version using the Add and Remove Programs utility in the Windows® Control Panel.
2. Download and run the Catalyst installation package. Note: Installation on a partitioned drive is not recommended.
3. Proceed through the installation steps provided in the setup package to install Catalyst on the local machine. After installation, a program shortcut is placed on the desktop and in your Programs group.
4. Repeat the steps above for each required client installation.
5. To activate the product, submit your registration information as described in the Product Registration help topic.

Network Installation

1. Create a Catalyst folder on your network server with Full Control permissions for the Catalyst users or user group.
2. Move the Catalyst back-end database files from the Catalyst folder on the client machine to the network server machine. For the Microsoft Access® back-end database, move the mdb files that include a “_be” reference in the file name. For the SQL Server® back-end database, move the mdf and ldf files. Note: Please link to the non-sample database (i.e. without the “StoreMore” name) to submit your product registration and populate your company data.
3. Establish a linked connection to a Catalyst back-end database file located on your server by opening Catalyst from a client machine. If the Select Company Data File screen does not appear, open it by selecting File > Select Company from the Catalyst main menu. For the SQL Server back-end database, the back-end database will need to be attached to SQL Server before performing this step. For more details, refer to the How do I attach a back-end database to SQL Server? help topic listed below.
4. To avoid having to establish a connection to your server on every client machine, you can copy the front-end database file after completing step 3 above to all client machines. Otherwise, you will need to perform step 3 on each client machine.
5. To enable user-level security so that each user logs into Catalyst with their own user name and password, refer to the instructions provided in the Enable User-Level Security help topic.

Back to Top

How do I setup Catalyst to run on the network?

To install Catalyst on the network, move the back-end database to a shared server location and establish a link from the client using the Select Company option.

When enabling user-level security with a separate login name for each user, the Catalyst workgroup file (Catalyst.mdw) will also need to be moved to the shared server location and the desktop shortcut modified to prompt the user for their login information at startup. Please refer to the help topic regarding 'Enabling User Level Security' for more information.

Back to Top

How do I relink to a different back-end database?

Catalyst automatically detects broken table links when the database is opened and prompts the user for the new back-end database location and file name. To relink to a different back-end database file, choose File > Select Company from the Catalyst menu, select a different back-end database, and click the 'Refresh Links' button. The instructions vary depending on whether you are linking to a Microsoft Access® or SQL Server® back-end database. Refer to the Select Company help topic for more details.

Back to Top

How do I attach a back-end database to SQL Server?

The Catalyst SQL Server back-end database files are installed in the Catalyst application path during program installation. In a multi-user network environment, the back-end database files need to be moved to a shared folder on the server machine. If you do not already have SQL Server® installed on the server machine, you will need to do so before continuing with the setup. The steps below provide instructions on how to attach the Catalyst database files to SQL Server using either the client tools in SQL Server or the utility in Catalyst Manufacturing.

SQL Server Enterprise Manager or Management Studio

1. Open Enterprise Manager (SQL Server 2000) or Management Studio (SQL Server 2005 and 2008).

2. In the Console Root, expand your SQL Server group, right-click the Databases folder, and select 'All Tasks > Attach Database' or 'Attach...' from the shortcut menu. On the Attach Database screen, select the browse button (… or Add...) to search for the Catalyst .mdf file on your server. Select the file and click the OK button to return to the Attach Databases screen.

3. Click the OK button to attach the selected database. If an error occurs, verify you have the appropriate SQL Server permissions to perform administrative functions. After the database has been attached to SQL Server, you can now link to it from within Catalyst using the Select Company screen.

SQL Server Configuration Manager (for SQL Server 2005 and 2008)

1. Install SQL Server Native Client on each client machine.

2. Open SQL Server Configuration Manager.

3. Select SQL Native Client Configuration. SQL Native Client is the network library that client computers use to connect to SQL Server, starting with Microsoft SQL Server 2005.

4. Select Client Protocols. Enable the client protocol(s) in use by your networked client machines. For most networked environments, the client protocol will be TCP/IP. Shared Memory should be enabled when connecting to a SQL Server instance on the same computer. Please refer to SQL Server Configuration Manager Help for more information.

Back to Top

How do I configure Catalyst for use in a multi-user environment?

After installing Catalyst on a client machine, perform the following steps:

1. Create a Catalyst folder on your network server with at least Read/Modify permissions, preferably Full Control.

2. Move the Catalyst back-end database files from the Catalyst folder on the client machine to the network server machine. The Microsoft Access® back-end database files have a mdb file extension and include the “_be” reference in the file name. The SQL Server® database files have a mdf file extension and are matched with database log files having an ldf file extension. Note: There are two back-end database files included with the standard Catalyst installation – one with sample data that includes ‘StoreMore’ in the file name and an empty database without sample data. The empty back-end database is provided for you to populate your company data. The sample database is provided for evaluation and education purposes. Note: It is advisable that you remove the back-end database files from each of the client machines to avoid unintentionally updating a local file.

3. Open Catalyst Manufacturing front-end database using the desktop shortcut. If not automatically prompted to relink to a different back-end database, select File > Select Company from the Catalyst menu.

4. The instructions for linking to a back-end database vary slightly depending on whether you are connecting to a Microsoft Access® or SQL Server® database. For more details, refer to the Select Company help topic. Note: To avoid having to establish a connection to your server on every client machine, after relinking one front-end database to the server, you can close and copy that file to the other client machines you have already installed Catalyst. The file stores the established table link properties.

5. To enable user-level security so that each user logs into Catalyst with their own user name and password, refer to the instructions provided in the 'Enable User-Level Security' help topic. The Catalyst workgroup file (Catalyst.mdw) will also need to be moved to the server in this process.

Back to Top

Can Catalyst be installed for use at multiple physical locations?

Since Catalyst uses Microsoft Access as it's host application, the standard configuration consists of the front-end database residing on a client machine and the back-end database residing on a server machine within a local area network. However, with proper consideration given to bandwidth and security, however, it is possible to place the back-end database on a remote server to be shared by multiple physical locations. In this configuration, it is highly recommended that you use a SQL Server back-end database instead of an Access back-end database to avoid the risk of database corruption.

Catalyst was designed for use by a single company so if sister companies wanted to share the same back-end database, there would also need to be consideration given to the setup and use of data.

Back to Top

Can Catalyst be installed in a Citrix® or terminal services environment?

The Microsoft Access database files on the client PC include local tables updated by each user. In a terminal services environment, these local tables become shared unless a local copy of the Access database files is created for each user. A 3rd party utility program called Auto-FE Updater may be installed to overcome this limitation. In addition, it's possible to add a logon batch file to create a local instance of the Catalyst database files when the users connect to the terminal server through Citrix. The terminal services environment is not fully supported, but is possible to establish.

Back to Top

Can Catalyst be installed on a Windows 64-bit operating system?

Yes, Catalyst can be installed on a Vista or Windows 7 64-bit operating system. When opening Catalyst for the first time on a 64-bit machine, it will be necessary to relink the local database (Catalyst Local.mdb) to include (x86) in the Program Files path.

Back to Top