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

# Re: GEMS 1-17-15 Monitor Script created with erroneous data

- To: <bugtrack@dieboldes.com>
- Subject: Re: GEMS 1-17-15 Monitor Script created with erroneous data
- From: "Talbot Iredale" <tiredale@dieboldes.com>
- Date: Thu, 11 Oct 2001 14:14:34 -0700
- References: <052101c14d3a$219920d0$0a04a8c0@dieboldes.com>

The database referenced only had the jurisdiction wide script defined so I cannot be certain what the problem was. I think the problem was that a baseunit was selected rather than a reportunit since these were incorrectly displayed in the list box.
The system now only displays district in the district list box and precincts in the precinct list box.
This will be in GEMS1-1-7-17 and GEMS1-18-5.
Tab

> ----- Original Message -----
> From: Nel Finberg
> To: Bug Track
> Sent: Thursday, October 04, 2001 6:07 PM
> Subject: GEMS 1-17-15 Monitor Script created with erroneous data

> An election is defined for with one central count vote center returning results to polling precincts. A monitor script is defined as jurisdiction wide, for all races in the election. A batch of four ballots is counted centrally. JResultClient displays the contents of the monitor script as expected.

> A second monitor script is defined for one precinct only. Results Server creates a script file containing correct data for the first monitor script; the second script file contains erroneous data.

> The database 'El Paso, CO' is located on maryann//d:/program files/gems/backup.

> Posted on behalf of Mike Brown in El Paso County, Colorado.

> Nel

- References:
  - GEMS 1-17-15 Monitor Script created with erroneous data
    - From: "Nel Finberg" <nel@dieboldes.com>

- Prev by Date: RE: GEMS 1-17-16 Audit Log
- Next by Date: Re: GEMS 1-17-16 races with registered write-in candidates
- Index(es):
  - Chronological
  - Thread