[Date Prev][Date Next] [Chronological] [Thread] [Top]

# Re: 1.17 upgrade fails

- To: <bugtrack@dieboldes.com>
- Subject: Re: 1.17 upgrade fails
- From: "Tari Runyan" <trglobal@earthlink.net>
- Date: Fri, 1 Sep 2000 11:44:14 -0600

it is handled - tari -----Original Message----- From: Steve Knecht <skglobal@earthlink.net> To: bugtrack@dieboldes.com <bugtrack@dieboldes.com> Date: Friday, September 01, 2000 11:30 AM Subject: Re: 1.17 upgrade fails Will Marin be affected if they first created their DB in 1.14.n, then upgraded to 1.16.n for their artwork, but we want them to go to 1.17 for the election and update of SOS report? ----- Original Message ----- From: Ken Clark To: bugtrack@dieboldes.com Sent: Thursday, August 31, 2000 4:29 PM Subject: 1.17 upgrade fails Databases that were created with 1.11 through 1.15 fail to upgrade from .16 to .17 with "Field 'ExportId' already exists in table 'CandVGroup'" Ken

- Prev by Date: RE: 1.17 upgrade fails
- Next by Date: GEMS 1.16.9 - Creating new DB
- Index(es):
  - Chronological
  - Thread