If you are viewing this afterf updating from Bike Logs version 1.0.5 to 1.0.6, please be aware that there is a dedicated support article designed specifically to show how to quickly resolve this issue

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

The database structure is most commonly updated by later versions of Bike Logs which may incorporate new features that require new tables or fields to be added to the database.

The update process, if it is required, is normally fairly quick and the status bar in the startup 'splash screen' window will indicate the progress of the update procedure. Once the update has completed Bike Logs continues to load as normal.

However, in some situations, an error message similar to the image below may be displayed once the update process has completed.

The message indicates that, after attempting to restructure the database, the modified database was still not in the state Bike Logs was expecting.

In some circumstances this message may be expected:

If you are using the latest version of Bike Logs (and have not manually customised the database), this warning indicates that there was a problem with the automatic update process. In most cases, if the update fails once, it will fail from then on resulting in the above message every time Bike Logs starts.

The inbuilt database maintenance tools can be used to sort out issues with the database structure that the automatic update process is unable to process. For more information please review the 'Using the built in tools to fix database structure issues' article.