Release Notes for Mira V4.0.25 V4.0.25 Release 4 07/02/2011 (Current Version) 1. Several Minor bug fixes 2. Fix to the Mira4.exe Graphing modules to correctly output the full range of days for production plots These would incorrectly start at the day of first production and end at last day of production. Plots now honour the start and end date specified even if no production during the period. 3. Fix to the ISMS_Charts.dll to correct the range of dates plotted for the weather. Some plots were 1 day short. V4.0.24 Release 4 05/21/2011 (Current Version) 1. Fixed Several Tooltips to correct old ISMS references to read MIRA 2. Fixed a bug in the HSE log tables where it was possible to have the first few Days of project missing in log. This was the result of not opening the HSE Log at least once on the first day. 3. Fixed up the Zip/Unzip function - data compression options. Note that Zip/Unzip routines require database pathnames to not have any spaces. 4. Fixed problem in the Data record export function. This was getting an invalid database name to export from/to. This bug caused a confusing prompt to choose a database type to be opened followed by a crash on cancel. This bug was also effected by database pathnames with embedded spaces. 5. Fixed the allowed length of Source Volume from 4 to 5 digits to handle array size greater than 9999 Cu Ins. V4.0.19 Release 4 03/16/2011 (Previous Version) Field Release 1. Recompile V4.0.18 with minor cosmetic correction. V4.0.18 Release 4 03/02/2011 (Previous Version) Beta Release 1. Removed Call to DBEngine.Repairdatabase. Found that this method is now not supported under DAO360/Jet4 However the Call to DBEngine.CompactDatabase does both a repair and compaction under DAO360/Jet4. Both the Compact and Repair menu items now just call the new more robust Compactdatabase method. 2. Added a message box on completion of successful repair/compaction to inform the user that task succeeded. This was not always obvious. 3. Bugfix in HSE log. The Log was generating errors when encountered null values in database. 4. Changed methods for calling EXCEL used when generating plots/graphs. Original method used references to specific versions of excel libraries. Added Excel constants in declares section and changed Excel declares to 'object'. Removed references to Excel version specific libraries and implemented late binding. This allows plots and graphs in excel to be completed by whatever the current version of Excel is installed. V4.0.15 Release 3 02/17/2011 (Previous version) Beta Release 1. Implement variable Font size selection - add selectable fontsizes to Tools/Option Menu. Font sizes are now stored in the mira4.ini for Heading1,Heading2,Heading3,Large,normal,medium,small and Very Small. Standard font sizes from 4 to 26 are selectable for each. Preset Default sizes can be restored with a command button. 2. Fixed Default font sizes to properly display reports in Office 2007. 3. Bugfix several of the Predefined Report selection reports. 4. Rewrite many queries to Prevent popup errors occuring on opening empty tables. 5. Fix Predefined wizard start/end date options on Wizard form so they initially equal the correct Start/End dates for the Database if the database is from a previously completed survey. These were originally setting to the current date. If Database is a current project then the start/end date on the selection form will equal the current date. V4.0.13 Release 3 02/13/2011 (Previous Version) Beta Release 1. Bugfix to replace older VB5 Date/Time calculation format statements not supported in VB6 2. Fix to Midnight Shotpoint calculation 3. Remove the clock bitmap on status bar. Change font to Adobe. Fixed Box sizes for readability. 4. Correct misspelled URL 5. Fix access permissions on RPSQCX install folders in the Installer to allow access by all qualified users. V4.0.8 Release 1 02/07/2011 Beta Release 1. Rebranded All forms to RPS 2. Ported/Updated all code and OCX references from VB5 to VB6. 3. Updated all programs to use DAO360.dll and Jet 4.0 Database. This is a standard install in all OS after Win2k. Installing MDAC components no longer needed. This allows opening/converting a copy of the database with current versions of Access. All references to DAO350.dll and Jet 3.5 are removed from the program. 4. Updated the Installer and default install location to C:\RPSQCX\Mira This reduced installation issues on Vista and Win7 64 bit systems. 5. Dropped installer support for Win95,Win98 and WinMe. Minimum OS system is Win2k SP4 6. Updated database object references in all VB6 code to specifically identify DAO.[Object]. This prevents conflicts when opened in Access 2000 and later or calling Access runtimes. 7. Updates to Sheriff and Dinkey Dongle drivers to support WinXP,Vista and Win7 32 and 64 bit systems. Resolved confusing licensing path issues. 8. Updates to Mira Help, Users Manual and Beginners Guide. 9. Converted older .HLP file to Compressed HTML .CHM format. This saves having to install the .Hlp update on 64 bit systems. 10. Increased the maximum number of user defined Custom fields from 10 to 20. 11. Several minor bugfixes to Custom Report generation to prevent errors when null data or invalid date. 12. Redesigned Log and data input forms to improve use on larger high streamer count 3D jobs. 13. Updated the mira4.ism new database template to remove ECL logos and Exploration Consultants name from Reports. This was replaced with 'RPS' in Footers with no embedded logos. 14. Retained support for existing V3.5 and earlier databases. Known Issues: 1. When Opening existing databases from ECL then reports etc may still have ECL/Exploration Consultants Logos and name on footers. 2. The Seismic Log Report and Navigation Log Report Print options must still be done by opening a copy of the database in Access. Instructions on how to do for final report generation are provided in the Mira User manual. (Note: These functions will be moved fully to the VB code in the next release.) 3. Several issues that were present in V3.5 are still present in V4.0.8 These will be addressed in future releases. 3. Install on most systems requires Admin priveleges. The installer takes care of this and will request permission at start of install process. If installing on a contractor PC you may need to have the PC admin/Crew IT person provide the permissions. If installing internally on an RPS system you may need to contact the IT department. Feedback: While a lot of testing was completed prior to release there may be issues that were not detected. Please provide feedback on any bugs, errors or problems you encounter to glanvilleg@rpsgroup.com or to Mira_Support@rpsgroup.com