Skip Navigation LinksZCS Homepage 4 CASE*track 2 Support 4 CASE*track 2.10 Upgrade

We have discovered a problem with this upgrade. Before applying the upgrade, please perform the following check:

  • Using 'My Computer',  look in the folder C:\Program Files\Casetrack and confirm the file CT.MDW is there
  • If it is there, continue with the upgrade as described in the release note
  • If it is not there, copy it to there from the folder on the upgrade CD at D:\install\server (assuming D: is your CD drive)
  • Once it is copied, perform the upgrade as described in the release note.

If you have already attempted to upgrade, and received an error message 'The workgroup information file is missing or opened exclusively by another user' or 'table mattertypes cannot be found' there's more info on this issue here.  

Please accept our apologies for the inconvenience.

. . .and another problem

There is also another, unrelated, known issue with this release.  If the upgrade goes through perfectly, but you receive an error of the form 'Item cannot be found in the collection corresponding to the requested name or ordinal. [3265]'  when viewing a matter in the Case Details window, then please refer to ref 440 here

To Roll Back the Upgrade Completely

To roll back the 2.10 upgrade to 2.9, eg if you find you need some more reports in the old format, follow the steps below:

Automatic backups of the database and program are created by the upgrade process.
They are marked with a year-month-day-hour minute filename - Eg for upgrade done at 9:30 in the morning of 2nd April 2007, there would be a database backup file ct200704020930.mdb and a program backup ct200704020930.exe

Therefore to roll back to the previous version:

  • Using 'My Computer' locate the live database file - normally named CT.MDB and located on your server on a network version, on your c:\program files\casetrack directory on a stand-alone - and rename it to CTnew.MDB;
  • Similarly locate the database backup file - ct200704020930.mdb in our example - and rename it back to CT.MDB
  • Rename the program file c:\program files\casetrack\casetrack2.exe to casetracknew.exe
  • Rename the backup program file  - ct200704020930.exe in our example - back to casetrack2.exe

You should then be able to run reports using the old codes.   You can upgrade to 2.10 again using the 2.10 upgrade CD.

Alternatively, if you have not added or changed any data, you will be able to roll forward to the new version again by renaming the CTnew.MDB and casetracknew.exe files back to CT.MDB and casetrack2.exe respectively.