Managing your rowing log
Your RowPro rowing log is one of the most important parts of RowPro, and like any important resource it needs to be managed well. The list below is designed to help you manage your RowPro rowing log effectively:
As you continue to add entries to your rowing log, it gradually becomes an ever-more-precious record of your rowing history, one that you would be very sorry to lose. There are several ways to do this:
There's nothing quite like having a hard copy of your rowing log on paper, in the event that your entire PC dies and you discover your backups are inadequate. Of course if you needed to re-enter a long list of rows from paper ... See the Rowing Log Help Topic for details.
This enables you to save a soft copy of your rowing log in .CSV format suitable for importing into programs like Microsoft Excel. This enables you to re-enter the information electronically without having to type it all again. See the Rowing Log Help Topic for details.
Concept2 provides free Online Logbooks where you can record all your rows. RowPro enables you to select multiple rows in your rowing log and export them direct to your Concept2 Online Logbook. See the Rowing Log Help Topic for details. In an emergency, Digital Rowing can help you use entries from your Concept2 Online Logbook to rebuild your RowPro rowing log.
This enables you to restore your RowPro rowing log in full is there is a problem, provided your backup wasn't lost at the same time as your RowPro database. See the Managing your Database Help Topic for details.
If you row with your LogCard inserted, the PM3 will automatically save your results on the LogCard. If you save these LogCards, you can later import the results from them into your RowPro rowing log. This has the advantage that splits are available for Continuous rows, however it has the disadvantage that Interval rows are saved on the LogCard as a series of individual rows, one for each interval.
As you continue to add entries to your rowing log, it gradually takes up more disk space. The factor that makes it grow fastest is saving strokes. If you always save strokes you can later use any entry in your rowing log to animate a boat in another lane, so always saving strokes gives you great flexibility. However always saving strokes also grows the size your database fastest. In say a 2,000m row, there will be say 20 split entries and 1 totals entry, but there will be around 200-250 stroke entries, so if you save strokes the entry will be 10 times as large as if you don't. And for a Marathon row it will be 200 times as large if you save strokes! The main strategies for dealing with this are:
Save strokes only for rows you think you might want to use to animate a boat in future, rather than saving strokes for every single row. To do this, either:
|•||Uncheck the Save strokes by default checkbox on the Control Center / User Settings page, and then check the Save strokes checkbox at the end of each row for which you want to save strokes, or|
|•||Check the Save strokes by default checkbox on the Control Center / User Settings page, and then uncheck the Save strokes checkbox at the end of each row for which you don't want to save strokes.|
Once in a while comb through your database, identify and select rows with stroke data saved that you no longer want stroke data for, and delete the stroke data from those rows. To delete stroke data from your database:
|•||Identify the rows with saved stroke data - these have 'SD' in the SD column to the right of the rowing log.|
|•||Select one or more rows whose stroke data you want to delete, then right-mouse and click Delete Strokes.|
See the Rowing Log Help Topic for more information.
You can only row with your past self if the row(s) you use for this have stroke data, so think carefully before you delete saved stroke data to make sure you only delete strokes from rows you no longer want to row with.