Could not creating supplement table
A bug in the table design form was preventing users from creating supplement tables.

Could not add a new supplement name
The updated supplement table structure has been corrected.

The HTML report has been corrected and the default template updated.

Copy Previous Record and Copy from Template
There is now an option to select whether or not to include the species name fields when copying from the previous record or from a template

Photos and Maps not working
The photo and map working functionality has now been corrected.

Family code has been deprecated and replaced with the new Family Name Identifier.

Registration details dialog box in the installation problem did not always show in front of the main installation screen.

Entering co-ordinates in UTM produced a shift in the co-ordinates when converted to decimal degrees. The collecting book currently only stores co-ordinates in decimal degree format, but will be updated later to store the co-ordinates as entered by the user. In the mean time the co-ordinate conversion routines have been revised so that there is no shift in the co-ordinates when converting between decimal degrees and UTM.

Users can now specify if they want to see just names that have been added to the master list, rather than including any name updates.

If columns in a data table had been re-orderd, using Ctrl+D (copy from the field in the previous record) produced unexpected results.

Re-instated the context menu for the full species name displayed at the top of both the data table and collecting book forms.

Fixed.

Species name fields were deliberately not being copied when duplicating a collecting book record. This has been modified so that now they are.

Confusion relating to the fact that the collecting book setting is table specific. This setting has been added to the table design form to make it more obvious to the user.

Copying the previous field was not consistent depending on whether the user had pressed the Insert key to get a new record in a data table, rather then clicking the + button on the navigation bar. Functionality between the two has now been made the same.

This error was caused by the MySQL ODBC driver not being configured properly. The options "Don't Optimize Column Width" and "Return Matching Rows" need to be select in the MySQL ODBC DSN Configuration.

The more information dialog box was producing access violations when connected to a non-microsoft access database. These have been corrected. This problem was probably introduced when fixing ISSUE-0000930. Errors also occurred when scrolling through a query result set.

If the current record in a collecting book was being edited when the user clicked on the "Add Field" button on the last page of the collecting book, then any pending changes were lost. The current changes are now posted to the database before allowing the user to add a new field. A similar issue applied to switching between form view and datasheet view, with the same resolution.

If the user was trying to import a Microsoft Access table that contained a boolean field, refered to as a Yes/No field in Microsoft Access, then an exception was produced. Max was not correctly recognising this type of field in the source table, so could not create the destination table for the data.

A button has been added to the toolbar to give the users a quick method of adding a name to the supplement table.

There is an option on the print labels dialog box for the filename to be displayed on the label. This had no effect. Now when the user selects this option the name of the Microsoft Access database is added to the bottom of the label, followed by the name of the collecting book in brackets.

A new function has been added to the collecting book where the user can populate details of the record from the template database by selecting from a list of values. Ctrl T initiates the process. Several issues were encountered during the development of this process, all of which are now resolved.

The existing coordinate conversion from geographical to UTM coordinates was rounding the UTM coordinates to 3 decimal places. This rounding has now been removed.

When entering new records into the collecting book template table, the collector number was being incremented. This should not have been occurring and has been fixed.

When the user creates a new table from the table design form, they are prompted to enter a name for the new table. If a table already existed with the same name then an exception occurred. Now a check is done to see if there is a table with the specified name and if so the user is prompted to replace the existing table. If they choose not to do so, they are returned to the dialog box where they can specify a different table name.

There are several fields in the collecting book where the user enters the value via a drop down list. Originally there was no null or empty value in the list if the user wanted to clear the value of the field. Pressing the Delete key whilst the control had focus worked, but was not obvious. A blank entry has now been added to the top of the list to clear the field.

The status line for secondary name identifier fields was not updating properly if the master list for the secondary name was different to the primary name identifier. The name for the secondary name identifier was being looked up in the wrong master list.

The Max update utility would not update the users version of Max if they were using an evaluation serial number. This has now been changed.

The Max update utility produced an exception if Max was not already installed on the users machine. Now the user is notified that they need to install Max before running any updates. The utility then terminates cleanly.

The CSV export files for used to import the data into WAHERB were being incorrectly produced with the leading zeros on the sheet number field.