|Title||Can't update cases in a TeamTrack database upgraded from 4.5 to 5.0|
|Assigned user||Gareth Rees|
|Description||The P4DTI crashes with an access violation if it attempts to read certain records in a TeamTrack 5.0 database that has been converted from a TeamTrack 4.5 database.|
I was running TeamTrack 4.5 (build 4509) with a sample database that I had created and used with the P4DTI. I installed TeamTrack 5 beta (build 5024c) and upgraded the database to the TeamTrack 5 format. The P4DTI would not work with this database (even though it had been recompiled with the TeamShare API for build 5024c). In particular, an attempt to read records from the database and then update one of those records caused an access violation in the TeamShare API.
|Analysis||This doesn't happen with a newly-created database in TeamTrack 5, suggesting that the problem may be to do with a corrupt TeamTrack 4.5 database or an error in upgrading it to TeamTrack 5.|
See  for instructions on reproducing the defect.
TeamShare sent us some information that may be relevant .
GDR 2001-06-30: TeamShare found a defect in the API that may be the cause of this .
|Created by||Gareth Rees|
|Created on||2001-05-31 16:50:03|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:43:58|
|History||2001-05-31 GDR Created.|
2001-06-30 GDR Referred to defect found by TeamShare.
2001-07-15 GDR Edited title and description for inclusion in release notes.
|13767||closed||2001-07-03 12:36:09||Gareth Rees||Added support for TeamTrack 5.0:
Split code/tsapi/... into code/tsapi-4.5/... and code/tsapi-5.0/... and split the Developer Studio project teamtrack.dsp into teamtrack-4.5.dsp and teamtrack-5.0.dspso that I can build two copies of the Python interface to TeamTrack, one for TeamTrack 4.5 and one for TeamTrack 5.0.
Updated teamtrack-module.cpp so that it has two entry points (one for each module).
Added teamtrack_version configuration parameter.
Updated design, Administrator Guide and release notes.