rptMart For CR - INSTALLATION INFORMATION
=========================================

This file contains information which may assist you installing rptMart for CR.

POSSIBLE CR VERSION CLASHES
===========================
rptMart for CR uses CR version 8.0.0.392 (20/04/06).
If it is installed on a PC where an older CR version is already installed then some CR drivers
etc. may be updated.

This shouldn't be a problem BUT...
To avoid any clashes we suggest you trial rptMart on a PC where EITHER...
   CR is not installed OR...
   CR version 8 is installed


DISK SPACE REQUIREMENTS
=======================
rptMart requires under 20Mb disk space when installed BUT during installation up to
40Mb (or more!) may be required.
The files are first extracted to a temporary folder (<Windows Temp>\$Inftool.tmp) before
being installed (so 2 copies exist during install).

Note that the Windows temp area is used (usually c:\windows\temp) so this drive requires
most of the free space (even if you are installing to another drive).

The 'or more!' may occur if Windows asks for more virtual memory during the install (this
depends on your VM setup).


POSSIBLE ERRORS
===============
The installation process should proceed without any errors. If any errors occur it
is important to rectify them as rptMart for CR will probably not run correctly.

Below are possible errors with reasons and solutions. Note that the solutions are
for specific problems.

IN MANY CASES IT MAY BE NECESSARY (AND SIMPLER) TO INSTALL AGAIN


TERMS USED BELOW
================
rptMart
rptMart for CR

BDE
The 'Borland Database Engine'  - used by rptMart to for its own database

BDEadmin
This is the program bdeadmin.exe ('BDE Administration' in rptMart menu).
If you installed from the 'No BDE' install then you can locate this in your BDE
installation folder.

rptMartBdeAlias
The BDE database alias named 'rptMart Internal Data'.
To work properly rptMart needs this alias to be installed correctly.


A. ERRORS DURING INSTALL
========================
Most possible errors are related to 'normal' problems eg low memory, lack of
network rights, corrupt registry database etc.
In all these situations fix the problem and install again.

***Setup asks for Disk #?
      This can happen if Windows has become 'confused' through other programs prior to installation
      Possible fixes are
      1. Tell the installer where the data is and continue the install.
          The data is in <Windows temp directory>\$INFTool.tmp (ie. usually C:\Windows\temp\$INFTool.tmp)

      2. OR quit and install again after restarting Windows

***Out of Disk Space Errors
      Lack of disk space can cause several unexpected errors.
      Check the available disk space If there are errors during install.
      See 'DISK SPACE REQUIREMENTS' above

***Warning - BDE Alias Setup ERROR
   This occurs when trying to add the rptMartBdeAlias.
   Possible reasons (and fixes) are
   1. BDE is not installed (at all or properly)
      Check this out by running BDEadmin (simple, but unfortunately not conclusive).
      BDE 5.0 or above must be installed on the PC. This happens automatically
      if you install from the full rptMart install. If you installed from the
      'No BDE' install then you need to either install BDE yourself or download the
      full install and use it

   2. rptMart has been installed on the PC before
      The install process tries to add rptMartBdeAlias - even if it is already present.
      If you installed to the SAME folder as the previous installation then everything
      is probably ok.
      If not then use BDEadmin to edit the 'PATH' property of rptMartBdeAlias to
      <InstallFolder>\Data (or wherever the rptMart data is).

***Network initialization error
      This occurs on re-installation where the previous installation no longer exists and
      the current value of rptMartBdeAlias is not valid.
      This is because BDE checks the old value (for active files etc) before changing it.
      If you installed to the SAME folder as the previous installation then everything
      is probably ok.
      If not then use BDEadmin to edit the 'PATH' property of rptMartBdeAlias to
      <InstallFolder>\Data (or wherever the rptMart data is).


B. ERRORS/PROBLEMS ARISING FROM PARTIAL OR FAULTY INSTALLATIONS
===============================================================
***An error occurred while attempting to initialize the Borland Database Engine (error $2109)
      This occurs on entering rptMart and is because the BDE is not installed (at all or properly).
      See the above notes for solutions.

***Unknown database alias 'rptMart Internal Data'
      This occurs after attempting to logon and is because rptMartBdeAlias is not present.
      Use BDEadmin to add the alias ('New', from 'Database' Tag) with these properties
      Type: STANDARD
      DEFAULT DRIVER: PARADOX
      ENABLE BCD: FALSE
      PATH: <InstallFolder>\Data   <== ie. the folder where rptMart's own data is stored

***Network initialization failed - Path not found
      This occurs after attempting to logon because the path in rptMartBdeAlias is not valid.
      Use BDEadmin to edit the 'PATH' property for rptMartBdeAlias to where your rptMart
      data is (usually <InstallFolder>\Data)

***Cannot add the first user
   Check the above messages for possible causes
   1. You had the 'Warning - BDE Alias Setup ERROR' (see above)
      BDE must be running ok for rptMart to save your entries. Get this error fixed
      and run install again

   2. Other - use BDEadmin to check and edit the 'PATH' property of rptMartBdeAlias
      to <InstallFolder>\Data (or wherever the rptMart data is).

***Too many passwords
      This occurs before logon and is because the data password is incorrect (note that
      the message text is misleading).
      Either the rptMart registry entrys and/or its data files are damaged or mismatched.
      This can happen when installing a new version over an existing registered copy. In
      this case rptMart uses your registered name/# (stored in registry) and the data files
      of the unregistered trial version (and produces this 'error').
      See the 'Upgrade Procedure' Help file topic for details on the correct upgrade procedure.

***Various sharing violations - especially under Win95
      May occur at any time (infrequently?, depending on other applications being used)
      Use BDEadmin to set 'LOCAL SHARE' to FALSE (in Configuration/System/INIT area)

