There are several items that can be changed on this window. Select a group of options by clicking on one of the tabs at the top.
Files
Tell ElkRP where to find the various files it needs:
• The Operators Database contains the operators’ names and passwords. It may be kept anywhere on your disk or on the network. A shared network drive is recommended if multiple operators will be using ElkRP on more than one computer. If you have a single computer dedicated to ElkRP, however, it would make sense to keep this file in the RP folder.
• The Controls Database contains information pertinent to every model of system ElkRP can communicate with. It may be kept anywhere on your disk or on the network. A shared network drive is recommended if multiple operators will be using ElkRP on more than one computer. If you have a single computer dedicated to ElkRP, however, it would make sense to keep this file in the RP folder.
• System update files (bin files) are product updates released by Elk Products from time to time. They should be stored together in the same folder. Specify the folder where you keep them in the box provided. A shared network drive is preferable if they are to be accessible from more than one computer. Otherwise, create a new folder in the RP folder and keep them there.
• The log file contains a history of who used ElkRP, what they did, and when they did it. It is named ElkRPLog.txt, and is located in the RP folder. The log file continues to grow with every use of ElkRP. ElkRP will warn you when it reaches a certain size limit. Select any size limit between 16,000 (16K) and 64,000,000 (64M) bytes. If you have a small hard disk and don’t use ElkRP often, a lower number will suffice. If your hard disk is large and ElkRP is used daily, you should specify a larger size. As a general rule of thumb, when printing the log file, it takes approximately one printed page per 3300 bytes. So, if the log file is 100,000 (100K) bytes when printed, the printout will be approximately 30 pages long.
See also:
Connections
ElkRP has the unique ability to determine what differences (conflicts), if any, exist between the values programmed in a system and the values stored for that account in the Accounts Database. It can also determine whether the difference is a result of a change in the system, a change in the database, or a simultaneous change in both. On the Connections tab, select whether you want ElkRP to check for conflicts after it connects to a system, before it disconnects, or both. It is recommended that Check for conflicts when connecting be enabled. This gives you the opportunity to see and resolve any conflicts that exist before you begin sending and receiving other values.
See also:
RP Code
The RP Access Code is a security feature that prevents unauthorized connections to a customer’s system and prevents takeover by competitors. Click on RP Access Code below for further details. If you choose to program the same code in all your accounts, enter it on this screen. Then, whenever you create a new account, it will automatically be entered in the correct box on the New Account dialog screen. If you choose to program a unique code in each account, leave it blank here.
See also:
Database Security
Database security will help protect you company against someone copying your Accounts Database in an attempt to take over your customer accounts. If you leave the items on this screen blank, you will not be protected. To protect your accounts, enter a unique password in the Password box. When you enter a password, it is encrypted and stored in the Operators Database and the Accounts Database. The two must match before ElkRP will allow them to be opened.
The additional boxes on this screen are required. This information is encrypted and stored in the database. It is used to protect you. Should Elk Products ever be asked to reset a Database Password, we will contact you to confirm the request.
See also: