This article explains why the checksum mismatch appears after Bike Logs is updated from version 1.0.5 to 1.0.6 and what needs to be done to stop the warning appearing.

The first thing to make clear is that there is nothing wrong with the database and all of the ride, route and bike details you have entered will be safe. The warning is generated because your database contains two fields that were never used and have been removed for the latest version.

One of the first things Bike Logs now does when it starts up is to check that the database is in a usable state and, if it does not contain all the tables and fields that are needed, Bike Logs will automatically attempt to update it.

After updating the database the results are checked and the checksum mismatch error is displayed if the structure of the database does not meet expectations.

Because the automatic update process deals with creating new tables and fields and doesn't remove undocumented ones the two deprecated fields (LogHeartRate and RoutePointers) cause the structure check to fail and the warning is displayed.

In this particular case you can safely ignore the warning and Bike Logs will carry on working as normal but, as you are here reading this page, you would probably rather stop it appearing altogether.

To stop the warning appearing the deprecated fields will need to be removed from the database and this can be achieved using the 'Database Maintenance' option found in the 'Tools' menu.

There are some resources available on the web site to assist you:

The demonstration video is probably the most useful resource in resolving the problem, as it demonstrates the entire process from start to finish. The other articles may be of use if you would like more information.