If you are an existing HireTrack Eclipse customer then you may have one or more HireTrack Eclipse databases that you wish to upgrade to use with HireTrack NX.
The upgrade process is described further in the following pages, but before you start you should be aware of the following:
| 1. | The upgrade process can ONLY be run on a machine that is already able to successfully run HireTrack Eclipse. If you machine can not run HireTrack Eclipse, then the upgrade program will not run.
|
| 2. | The upgrade process will require you to know the path to the HireTrack Eclipse database that you wish to upgrade. This can be local to the computer running the upgrade process or can be on a network drive, however in the later case, the upgrade will take approximately 10% longer to complete.
The path can be found by running the HireTrack Eclipse multi-company utility.
The upgrade process make NO changes to the HireTrack Eclipse database, however in order to ensure data continuity, the HireTrack Eclipse database can NOT be in use by any other program whilst the upgrade process is running.
Note: We recommend that you take a copy of your HireTrack Eclipse company data (whilst no one if using HireTrack Eclipse) and then upgrade the copy. This will allow the data to be local (which will be considerably quicker ) and wil allow you to specify a short path to the data (the maximum permitted length of the path to the data is 65 characters).
|
| 3. | If the HireTrack Eclipse database uses consignments to track scanned barcodes then the upgrade process will need to know whether these are genuine consignments for a third party or whether they are simply a method to track in house barcodes to more detail than the HireTrack Eclipse default.
|
| 4. | HireTrack NX uses a different method to despatch and return equipment than HireTrack Eclipse. Each despatch or return utilises a prep bay and a despatch or returns note. During the upgrade process, these items are automatically created for any equipment lists that contain unreturned equipment. This can create an unnecessary overhead if you have many false "late returns". If all your late returns are genuine unreturned equipment, then you have no option but to process them all during the upgrade, however if your late returns are due to poor management of the late returns area of HireTrack Eclipse, then the upgrade process will give you the option to return all equipment that was over due before a specific date. You will therefore need to be aware of how your organisation has dealt with late returns in HireTrack Eclipse.
|
| 5. | Although most of the data is transferred from HireTrack Eclipse to HireTrack NX, there are a couple of notable exceptions.
|
| 6. | Attachments: Due to the mechanism Microsoft Windows uses to manage attachments it is not possible to automatically extract them out HireTrack Eclipse and transfer them to HireTrack NX, therefore if you need access to previous attachments we recommend that you refer to HireTrack Eclipse to access these
|
| 7. | Scrap Book: Due to the ephemeral nature of these enquiries, they are not transferred across to HireTrack NX.
|
| 8. | Although existing Crystal Reports template files will be installed in to the HireTrack NX database location, they won't be automatically upgraded to be compatible with HireTrack NX. This should be done from a workstation once the HireTrack NX client and more importantly the NexusDB ODBC driver has been installed and configured.
|
| 9. | Once the database has been upgraded the HireTrack NX database possible need to be moved to be local to the HireTrack NX server and will need to be configured with a suitable Alias. |
