Aquabase update to version 9.2.5.424

Aquabase update to version 9.2.5.424

The latest 9.2.5.424 update with a few bug fixes and some new functions is now available for download (Aquabase will check for an update on start-up) and will require a password to complete the update process. This password is included in an email to subscribers to the Aquabase Support and Development Programme. If Aquabase cannot download the update automatically you can also get it from the Download section of this website. You have to be a registered user to access the individual downloads in this section.

Please read the notes during installation for the latest exciting additions and bug fixes! We (the developers and the users) are constantly working on improving and fixing Aquabase functionality. Please let me know if you find any bugs and/or would like to make suggestions for new functions.

WHAT’S NEW IN THIS LATEST VERSION?

  1. The chemistry page report now only shows rows with parameters, if there are actually parameters (and not only the chemistry reference number CHM_REF_NR) with values for that row.

WHAT HAS BEEN FIXED SINCE THE LAST VERSION?

  1. The chemistry page report could return an error message with using a view to print chemistry for more sites than only the current site. The colours for the bands also did not adhere to the settings for the reports and some fields were not wide enough to display the values. The redox potential was also not shown under the physical properties. These have been fixed.
  2. When opening a workspace with SpatiaLite/Geopackage database right after having opened and closed a workspace with a server database (e.g. MySQL, PostgreSQL) an error could occur every minute due to the “server ping”, that was not closed properly on disconnecting the server database. This does not happen any longer.
  3. The lithology log report did not use the full available space on the page for the charts due to an incorrect calculation. This has been rectified.
  4. Several smaller, mostly unnoticed bugs, were also fixed.

Leave a Reply