The latest 8.2.3.375 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 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.
SO WHAT’S NEW IN THIS LATEST VERSION?
- The “Select Sites” dialog now also shows the Site Number together with the Site Identifier so that the entries in the list boxes are easier to identify.
- A trend line can be added to the time-dependent charts. This function is to be enhanced in future versions to allow trend lines for only parts (between dates) of the data in order to show several lines for different periods on one chart.
- The Piper chart has been enhanced so that the arrows are vectors (instead of normal lines) and are also showing in the series when opening chart properties, so they can also be switched off.
AND WHAT HAS BEEN FIXED SINCE THE LAST VERSION?
- If geometries in the Basic Information table (basicinf) were changed, e.g. by moving points in a GIS, a message would pop up when opening the workspace to inform the user that there are changed geometries and whether the user wants to update the coordinates accordingly. The user then has the option to update the coordinates or do it at a later stage under the Tools menu, or when opening the workspace again. When selecting to update the coordinates right there and then there was an error message, which lead to a failure to open the workspace, as not all initialisation settings had been set yet when trying to covert the Longitude/Latitude coordinates from the new geometries to the stored X_COORD/Y_COORD coordinates. This has been resolved by opening the basicinf table right at the end of the initialisation and after all the other validity checks have been done.
- Creating members from a View did not work as expected for PostgreSQL database connections. This is now working.
- A few smaller bug fixes and optimisations.