The latest 8.1.1.364 update with a number bug fixes and a few new features 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 download section.
Please read the notes during installation for the latest exciting additions and bug fixes! We are constantly working on improving and fixing Aquabase functionality. Please let me know if you find any bugs and would like to make suggestions for new functions.
SO WHAT’S NEW IN THIS LATEST VERSION?
- The time-dependent Discharge Rate columnar report has been implemented.
- The Basic Information Depth field is now checked so that it cannot be 0.00 (really…it does not make sense). This caused all kinds of other problems on other table entries, e.g. the aquifer depth fields (see below).
AND WHAT HAS BEEN FIXED?
- The refresh button of the top left Navigator on entry forms was disabled as this is the Navigator that scrolls through the current view, which is a read-only dataset. This has been enabled now again to refresh the view in case the underlying datasets have changed in any way by adding/deleting sites or running scripts.
- The Ctrl-Right and Ctrl-Left keys to move between sites did not work on all the entry forms as expected or with different key combinations. This has been fixed to be the same on all forms.
- The Aquifer Depth to Top and Bottom fields are now checked not only between themselves (bottom cannot be higher than top) but also against the Depth in Basic Information. If there is no Depth in Basic Information then only Depth to Top and Bottom will be checked. No Depth caused the latter to produce an error as the Bottom was automatically set to 0.00 when adding a new record and typing any depth into the Depth to Top field.
- The Setting of Constraints did not work as expected and has been fixed. It should work for the time-dependent reports as expected.
- A few smaller bug fixes and optimisation changes.