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

# RE: GEMS 1.11.2 - erroneous sequence numbers

- To: "Bug Tracking" <bugtrack@dieboldes.com>
- Subject: RE: GEMS 1.11.2 - erroneous sequence numbers
- From: "Ken Clark" <ken@dieboldes.com>
- Date: Mon, 30 Aug 1999 10:00:54 +0100
- Importance: Normal
- In-reply-to: <00cb01bef0cc$8d318520$0a04a8c0@maryann.dieboldes.com>

Dmitry, can you please look at this. Tari has mentioned this one before too. It sounds like we have situations where the sequence number field of VCenterReportunit is not being initialized. It should be set to the Reportunit KeyId when a new record is created.
Having said that, there isn't really a problem here. If you are not using sequence numbers, then the field is completely ignored by the system. We should probably hide the field in the list views in fact. If you are using sequence numbers, then you just need to regenerate them after you generate ballots (as usual).
Ken

> -----Original Message-----
> From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Nel Finberg
> Sent: Friday, August 27, 1999 9:42 PM
> To: Bug Tracking
> Subject: GEMS 1.11.2 - erroneous sequence numbers
> Precincts and districts but no races are defined in the attached database, originally imported from VTS. Both the Vote Centers with Reporting Precincts by ID and by Label reports indicate that many, but not all two-precinct vote centers are displayed with '1246576929' as sequence number for the second precinct. The sequence number column is otherwise blank.
> Precinct (and not sequence) numbers are printed on ballots, and ballot artwork has not yet been generated.
> Nel FInberg

- Follow-Ups:
  - Re: GEMS 1.11.2 - erroneous sequence numbers
    - From: "Dmitry Papushin" <dmitry@dieboldes.com>

- References:
  - GEMS 1.11.2 - erroneous sequence numbers
    - From: "Nel Finberg" <nel@dieboldes.com>

- Prev by Date: Re: AVTSIS 3.9.3
- Next by Date: RE: Runtime Error
- Index(es):
  - Chronological
  - Thread