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

# Re: GEMS reports versions

- To: <support@gesn.com>
- Subject: Re: GEMS reports versions
- From: "Tari Runyan" <trglobal@earthlink.net>
- Date: Tue, 13 Feb 2001 21:45:33 -0700
- References: <009c01c0952c$b2dab070$0a04a8c0@gesn.com> <00c401c09530$85cd0a70$0203a8c0@GES001> <3A8964BB.D8672C56@earthlink.net>

yup Tari ----- Original Message ----- From: Donald W. Biszmaier To: support@gesn.com Sent: Tuesday, February 13, 2001 9:45 AM Subject: Re: GEMS reports versions Tari: Were you using the 1-17-2 version of reports with the 1-14-13 gems when you checked the Anchorage database for not being able to print the "Jurisdiction Wide"? Thanks: Don Tari Runyan wrote: What I usually do is load the most recent reports - 1-17-2 then if I have to go back to a previous version of gems -I am ok Tari ----- Original Message ----- From: Nel Finberg To: support Sent: Monday, February 12, 2001 12:47 PM Subject: GEMS reports versions As our work involves working with different versions of GEMS, it also means retaining backup folders of corresponding versions of report files and copying the backup into the principal reports folder in order that the correct report files be recognized. Any ideas on streamlining this process so that we can change reports versions in the same way we vary between GEMS versions? Nel

- References:
  - GEMS reports versions
    - From: "Nel Finberg" <nel@gesn.com>
  - Re: GEMS reports versions
    - From: "Tari Runyan" <trglobal@earthlink.net>
  - Re: GEMS reports versions
    - From: "Donald W. Biszmaier" <dbglobal@earthlink.net>

- Prev by Date: Quarterly RCR report (was RE: Add The Choice "Write-in, if any" To Candidate Type Pull Down Menu)
- Next by Date: Re: Kansas Rotation Rules
- Index(es):
  - Chronological
  - Thread