General FAQs
I have changed my computer and wish to transfer CHASE from the old one to the new one. How do I do this?
1. Copy the CHASE data from the old computer. The three key files you need to copy are CHASE.MDB (Microsoft Access data file), CHASE.MDW (Microsoft Access workgroup file) and CHASE.CFG (configuration file). These should be copied onto a suitable storage medium before you finish using the old computer. These are normally in the My Documents\CHASEDatabase directory on your hard disk. The CHASE.MDB file is normally too large to copy onto a floppy disk. You may need to use a Zip drive or CD-ROM or a file compression program such as WinZip. For simplicty, it may be easiest to copy the the entire CHASEDatabase folder .
2. Install CHASE on the new computer but do not run it.
3. Copy the files from step 1 into the CHASEDatabase directory. They will overwrite the empty data files which were set up as part of the installation process.
You should now be able to start and use CHASE from the point you left it on the old computer. If you are asked for a serial number it probably means that you did not copy the files correctly. If you use a CD-ROM to transfer the files you should ensure that they are not marked as Read-only - many CD writers mark the file as read-only when writing it to the CD and this remains set when you copy it to the new computer.
Once the transfer is complete, uninstall CHASE from the old computer.
Can you tell me exactly which files are installed when I set up CHASE?
Yes. Click here for a full list.
I have CHASE Single-User system. It has been fine until now, when I always get the message "The user CfW is already logged on", even though I am the only user.
This can happen if the computer or Windows crashes and does not get the opportunity to delete the .usr file trhat controls access to CHASE. Look for a file called ~cfw.usr in the CHASEDatabase folder and delete it manually. This error does not occur with version 2.0.0 onwards.
I have CHASE for Windows set up on a network. It has been fine until now, when I always get the message "The user CfW is already logged on", even though I know it isn't as I am the only user.
You are running CHASE on the workstation with the data files (CHASE.MDB and CHASE.MDW) stored on the network server and CHASE can no longer find them. The error occurs because, when you log on, CHASE attempts to "lock" the user name so no-one else can use it and, if it fails, this is message you get.
There is a command line parameter included in the shortcut that starts CHASE for Windows which tells the CHASE.EXE application where to find its data. Either this shortcut has been modified so that the parameter is no longer correct or the directory name or network drive has been changed. Two examples: your data drive may have changed from E: to F: because a new CD-ROM drive, using E: has been added to your workstation; you may be a woman who has recently married and your data directory has been changed from your single name to your married name. A typical shortcut command looks like the example here.
"C:\Program Files\Hastam\Chase\Chase.exe" F:\JSmith\Chasedata
The first part (in quotes because the "Program Files" folder includes a space character) is the command to start CHASE for Windows, the second part is the name of the network directory where the CHASE.MDB and CHASE.MDW files are stored (ie the "Chasedata" subdirectory in "F:\JSmith"). Please refer to your Windows documentation for details of how to modify shortcuts.
NB: Error reporting is modified from version 1.2.020 to distinguish this condition from genuine attempt to log on twice. From Version 1.2.027, the user is also given the opportunity to browse for these files.
How does CHASE for Windows find its data files? I need to know this so that I can set up the network correctly.
When CHASE starts it looks for the CHASE.MDB file in the following locations:
(1) The CHASE program directory. If it is not found then it looks in
(2) A directory entered as a command line parameter in the shortcut. If there is no Command Line parameter, or it is not valid, then
(3) (from version 1.2.027) it checks the initialisation data for a location.
If none of these options leads to a valid path to the CHASE.MDB file then (from version 1.2.027 or later) the user may browse for the file using a standard Windows Open File dialog. When found, this value is stored in the CHASE initialisation data.
How can I backup the CHASE for Windows Data?
All your data is stored in two files - CHASE.MDB and CHASE.MDW. The first of these stores all the actual evaluation and module data, the second is the Microsoft Access Workgroup file which stores the user information and passwords. You should make regular backups of these two files using one of the many backup systems available. Windows 95 and 98 include a backup program (in Start|Programs|Accessories|System Tools|Backup) which will allow you to backup these (or any other) files to floppy disk or tape. Many other third-party systems are available, as are higher capacity removable media like Zip and Jazz disks. Do not rely on the File|Download function as this only copies module and evaluation data. The CHASE.MDB file includes other items, such as record number counters, which are not copied by the download process. Always make a backup copy of these two files whenever you do any significant amount of work in CHASE for Windows. Note that CHASE for Windows must be closed down when you backup the files otherwise it will prevent the backup program from accessing the data files.
How do I go back to an evaluation that has already been completed?
There are two routes.
1. Right click on the appropriate cell in the Allocation Window to bring up a context menu as shown on the right. This has as one of its options Open evaluation... which will list all evaluations for that area/module. The top one in this example is a current uncompleted evaluation; the remainder are previous ones that have been completed.
2. Open the Evaluations Window, select the View menu and click on Completed. This will list all completed evaluations, including summaries, by area or by module. (From version 1.2.006 use View|Display options... )
I have re-opened a completed evaluation and want to make changes to it but I cannot. Why?
When you finish an evaluation through the Tools | Finish Evaluation option the evaluation is "frozen". You cannot make further changes unless your User Name has the Verify or Administrator rights.
How do I save the settings I have set up in, for example, the print options?
You don’t have to. CHASE saves them automatically, together with your current analysis table set-up, whether you are displaying notes, guidance or recommendations on the evaluations screen, the weighting of the last question you edited, etc. Around 100 different settings are saved.
NOTE: These settings are saved with your User Name. Two different users may have different preferences and requirements and thus changes to settings you make will not apply to a different user.
Can I print in colour?
Colour printing is implemented for the graphics but not at present for text printing. Any colour selections you made when setting up fonts are ignored.
I want to copy the text from one question to another but when I click on the Copy and Paste buttons on the Toolbar nothing happens. How can I do this?
The toolbar is not always accessible - for example, when editing the text of a question - but it is still always possible to access the clipboard through the Windows 95/NT context menus. These are popped up by clicking the right mouse button. If you are editing text and want to copy it, select it with the mouse by holding down the left button and moving the mouse to select the text, then press the right mouse button to bring up the context menu. In a text field this menu will always include the Cut/Copy/Paste options.
I have written a new module and now want to give it to the other CHASE users in the company. How do I do this?
Use theFile | Download facility to make a copy of your module in a separate database file. This can be sent to your other users who can then use the File | Upload facility to incorporate it into their own systems.
I loaded CHASE for Windows on my colleague's machine as well as my own but when I created a module, downloaded it to a floppy disk and then uploaded onto his computer, it overwrote the module he wrote. What have I done wrong?
By installing a second copy onto another machine you broke the Software Licence Agreement which you accepted when you installed the program. You cannot move data between two installations made from the same system disk using the same serial number without generating errors. Contact HASTAM to arrange the purchase of a second copy of CHASE for Windows or a second serial number and licence. Significant discounts are available for second and subsequent copies.
CHASE always starts showing the Allocation Window. I would prefer it to start showing the Recommendations due Window. Can I change this setting?
Yes. Open the Recommendations due Window, click on the Window option on the main menu and select Set as Default. A check mark will appear against this option and CHASE will open this window on start up.
You can make any of the following windows the default: the Allocation Window, the Modules Window, the Areas Window , the Evaluations Window , the Analysis Table or the Recommendations Due Window.
If you prefer CHASE to start without opening any window, open the current default window and select Set as Default from the Window menu. This will clear the check mark and not assign it to any other window.
This setting is for your User Name only - other users may have different default opening windows.
I keep clicking in the Close Icon (X) by mistake and closing down CHASE for Windows when I don’t want to. Can I stop this from happening?
Yes, in Tools | Customise select Confirm program exit. If this item is checked, CHASE for Windows will ask you to confirm you want to exit before it closes down.
How can I find out the version number of my copy?
Click on Help and look in About CHASE for Windows. The version number is displayed in the bottom left of the window.
