Software Update - July 2005 We encourage current users of GOADS2005 to update their GOADS.EXE program files. The updated GOADS.EXE program file includes work-arounds for two minor problems that have been found and is inclusive of the corrections previously released in November 2004. It is not necessary to reinstall the program if it is already installed. Users can simply download the one file (GOADS.EXE) by clicking on "July 2005 Software Update" on the GOADS-2005 main website. Users should copy this file into their C:/Program Files/GOADS-2005/ folder and continue working without any loss of data. The old program file will be overwritten and no other modification is needed. If you have created multiple company folders, then also replace the program file GOADS.exe in your c:/Program Files/GOADS-2005/ folder and each company-specific folder that you may have created. The GOADS-2005 program should not be running when you update this file. For new installations of GOADS-2005, users simply should download the GOADS-2005.msi setup file by clicking on "Emissions Reporting Software (July 2005 Stand Alone Version)". The updated program file with corrections is included in the updated GOADS-2005.msi setup file. The software problems that have been addressed in this July 2005 update include the following: The program's QA function was not deleting obsolete error messages in certain instances, including when the user added comments to a flagged value that was later corrected and when a piece of equipment with existing error messages was deleted from the database. Previously-generated error messages are purged from the database with this July 2005 update for convenience. The program's QA function for checking each platforms total fuel usage against the sum of the fuel usage of its component equipment was malfunctioning. This QA check was found to be too simplistic and was disabled. Previously-generated error messages are purged from the database with this July 2005 update for convenience. The software problems that were previously addressed in the November 2004 update include the following (the November 2004 update is included in the July 2005 update software): The program's QA function for detecting duplicate equipment IDs was misidentifying some IDs as duplicates in certain cases. Many users will not encounter this problem as it depends on how the software is used. This has been corrected. We also found that 2 companies had grown to include platform/equipment lists far larger than any found in the 2000 inventory because of mergers. These exceeded certain program array size limits that were based on the 2000 data. The program arrays have been enlarged to fix this. We found that it was possible to enter duplicate platform data and cause a program failure. The detection of duplicate platforms has been made morethorough and now alerts the user before attempting to duplicate a platform that is already in the database.