watwarelogo
Home VeloLogger™ Support Troubleshoot Updates Tips Contact

Troubleshooting VeloLogger™ Software

Troubleshooting Topic 1

The following dialog appears:

Please Enter A Number

OR

Please Enter An Integer

Then the data that was just entered in the ride editor disappears and the editor is changed back to View Mode.

Solution:

Previous versions of the VeloLogger™ software used the default Microsoft Windows® validation for validating data in the ride editor fields.   Fields were only validated when the OK button was pressed in the ride editor.   When an error was detected, a dialog was displayed indicating that an incorrect value was entered.   As soon as the OK button was pressed on the Error dialog, the ride editor was closed and the edit was cancelled.   This did not give the user the chance to correct the field with the incorrect data.   Since the edit was cancelled and not saved, the user would have to re-enter all of the data for that ride again.

Download the Update Version 3.01 .   Follow the instructions on the page.

Troubleshooting Topic 2

The following problems exist:

Duplicate entries in the Weather Type Dialog

OR

No entries in the Ride Difficulty Rating Dialog

Solution:

The VeloLogger™ Update for Version 3.0 beta contained a bug that left the Ride Difficulty Table blank and created duplicate entries in the Weather Types table.

Download the Fix for Version 3.0 Beta.   Follow the instructions on the page.

Troubleshooting Topic 3

The following dialog appears:

Cannot Find COM object CoDbExt.dll

OR

Cannot Find COM object CoUnitCv.dll

Solution:

First check to see that the files CoDbExt.dll and CoUnitCv.dll are in your C:\Program Files\WatWare\VeloLogger directory (or the directory where you chose to install the VeloLogger application software during setup). If the files are missing then copy them from your install CD or your expanded download directory - probably the C:\Program Files\WatWare\Install directory. Then run the VeloLogger program again.

If you are running VeloLogger Version 2.0 then Download the Fix for Version 2.0 Follow the instructions on the page.

Windows® 95 and some 98 systems did not have the atl.dll file that was required to support the functions in the new VeloLogger™ CoDbExt.dll file.   The Fix for Version 2.0 is a new CoDbExt.dll file that does not require the Windows® atl.dll file to be located on the system.

Troubleshooting Topic 4

The following dialog appears:

Operation must use an updateable query

Solution:

This message indicates that the database file VeloLogger.mdb was marked as read-only.

You can correct the problem by removing the read-only attribute from the VeloLogger.mdb file.   You can do this yourself or you can download the latest version or update of the VeloLogger program and it will correct the problem for you.

To download the latest update for VeloLogger, visit the Updates/Downloads page.

To change the read-only attribute yourself, locate the VeloLogger.mdb file.   It will be located in the directory where you installed the program.   If you used the default directory during installation, it will be located in directory C:\Program Files\WatWare\VeloLogger.   Right click on the VeloLogger.mdb file and select Properties.   When the dialog box appears, uncheck the read-only attribute box.

Troubleshooting Topic 5

The following dialog appears:

ERROR Opening Registry Key (SetRootKey())

Solution:

This message indicates that VeloLogger™ is unable to write to your system registry.   The most likely cause for this would be that you installed and are running the VeloLogger™ software without Administrative privledges.

VeloLogger™ must be installed and must be run with privledges that allow you to install application programs and write to the Windows® System Registry.   The VeloLogger™ software will appear to install ok without proper privledges, but will issue error when you try to run the program.

Troubleshooting Topic 6

The following dialog appears:

ODBC Microsoft Access Driver Login Failed
Could not find file 'C:\...\VeloLogger.mdb'.

Solution:

This message indicates that the VeloLogger™ software cannot find the database file VeloLogger.mdb.  The database file is where all of the ride data and setup of bikes and components are stored.

If the file was removed from the directory where it was installed, try moving the file back.

If the file was deleted, you should restore your backup copy of the VeloLogger.mdb file, by copying it into the directory where the VeloLogger program was installed.

If the file was deleted and you do not have a backup copy of the file, you will have lost all of your logged rides, bike setups, and cyclist data.  You can either install the VeloLogger software again or copy a new VeloLogger.mdb from the Installation CD.  Either way, you will have to re-enter all of your data.

Troubleshooting Topic 7

The following dialog appears:

The Microsoft Jet database engine cannot find the input table or query '...'.
Make sure that it exists and that it's name is spelled correctly.

Solution:

This message indicates that the VeloLogger™ database VeloLogger.mdb is corrupt or that the system DSN (Data Source Name) has been changed and is connected to the wrong database.

To verify the DSN is correct, see Microsoft Windows help on the ODBC Data Source Administrator.  Under the System DSN there will be the Data Source Name VeloLogger that uses the Microsoft Access Driver (*.mdb) driver.  Check the configuration of this DSN to see that the selected database is VeloLogger.mdb and that it is in the proper directory.

If the VeloLogger database is corrupt, you should restore your backup copy of the VeloLogger.mdb file, by copying it into the directory where the VeloLogger™ program was installed.

If you do not have a backup copy of the file, you will have lost all of your logged rides, bike setups, and cyclist data.  You can either install the VeloLogger software again or copy a new VeloLogger.mdb from the Installation CD.  Either way, you will have to re-enter all of your data.

Troubleshooting Topic 8

The following dialog appears:

Data source name not found and no default driver specified

Solution:

This message indicates that the system DSN (Data Source Name) has been removed.  The only way to recover from this is to re-create the DSN or re-install the VeloLogger™ Software.  

If you choose to re-install, make sure you make a backup copy of your VeloLogger.mdb file and save it to another directory.  The install will delete all the VeloLogger files including your VeloLogger.mdb file.  If you do not make a backup copy, you will lose all of the ride data that you entered.  When you are finished with the new install, you can copy your backup copy of the VeloLogger.mdb file overtop of the newly installed file.  This will restore all of your old ride data.

To re-create a DSN, see Microsoft Windows® help on the ODBC Data Source Administrator.  Under the System DSN create a Data Source Name called VeloLogger that uses the Microsoft Access Driver (*.mdb) driver.  Configure this DSN and select the VeloLogger.mdb along with the full path.

[ Home | What Is | VeloLogger™ | Features | Demo | FAQ | Purchase | Support | Troubleshoot | Updates | Tips | Email ]

WatWare