Import VBA into your own workbook

[RJHug00]

For any of a variety of reasons, you might prefer to have this functionality in some workbook you already open on a regular basis. Just for openers, such an approach avoids the friction where Excel tries to protect you from malicious internet code [I'm not saying that this is inappropriate; I'm just saying that it happens at an annoying time when you're excited to use the new capability].

Once you've downloaded the .BAS files from this repository, incorporating them into a workbook borders on trivial.

1. Open your intended workbook in Excel (or Access or Word).
2. Press Alt-F11 to enter the integrated Visual Basic development environment.
3. Press Ctrl-r to ensure the VBA Project Explorer pane is open.
4. Find the VBAProject line for the intended workbook (there can be more than one if you have multiple workbooks open at once)
5. Right-click on that VBAProject line and choose 'Import File...'
6. Navigate to the folder containing the .BAS modules you previously downloaded
7. Double-click a .BAS file [you can only import one file at a time]
   <repeat steps 5 and 7 for the remaining .BAS files>

That's really all there is. Back in the Office application, if you press Alt-F8, you will see new macros, notably including 'ConvertPelotonRideToGarminActivity' which is the main one you want. However, recall from the Wiki page that this VBA code relies on environment variables, which you probably haven't setup yet, and will require the Office tool to be restarted when that has been completed.

Excel is going to allow you to import the BAS files into a normal non-macro-enabled workbook (i.e. one with a suffix .XLSX, but when you set about to save the workbook, Excel is going to warn you that the macro code you just imported will not be saved. To save your import efforts, change the type of Excel file to macro-enabled (i.e. an .XLSM suffix).

Note that setup instructions on the Wiki page refer to a button in the distributed workbook that runs VBA code to read a watch FIT file. You won't have nor likely ever need such a button, but instead you will have to run the 'DecodeWatchInfoFromFITfile' macro directly.