Originally Posted by Sleuth
If I remember correctly that option is for the entire waypoint list, irrespective of use. If you just have start / end points, and an internal routing without any waypoints / shaping points, the first recalculation performed by the GPS, will destroy the nice route you have created. It then defaults back to the fastest or shortest route whichever you have selected.
The easiest way to check if it is a waypoint or shaping point is to see if the point is listed as Park Road & Western Road (a junction) then it is a shaping point.
However there are more experienced Garmin users here, (I managed to be able to plan a route in MapSource & BaseCamp,) so if I am wrong - please feel free correct me!
If you transfer the route, and do not transfer the waypoints, the route will include the waypoints used to define your route (vias) but they won't show up as "favorites" on the device. This may or may not be what you want, depending on how you defined the route.
If you define your route using a bunch of waypoints, then I guess this way is as good as any of not getting a bunch of favorites on your device. An alternative way to create routes is to use waypoints only for origin and destination, and perhaps a planned stop along the way, then use shaping points to direct the route where you want it to go. Those are typically placed into the route using the "insert" tool (BaseCamp) or by selecting the route then rubber-banding to move the route through a point along a road or an intersection.
If you use MS or BC to build your route, the vias will be honored (whether or not you send waypoints) by the Zumo. (This is often not the case with 3rd party route building software.)
However, your should always build your routes in such a way so as to withstand recalculation by the Zumo. That means to place a sufficient number of vias in appropriate places to unambiguously define the route you want. If you set your software (BC or MS) routing preferences and avoidances to match your device's, you will get much more predictable results. For example, if you had BC set to "fastest" then downloaded to your Zumo which was set to "shortest", you are asking for trouble. The avoidances on the Zumo will not match exactly those in the software, and they will vary from Zumo model to model, but you can set them in a way that will not "clash".
It is possible to download a route to the Zumo without having it recalculate the route immediately, but depending on that is asking for trouble out on the road if you need the Zumo to recalculate for some reason (like you missed a turn, want to cut off a portion of your route to save time, want to divert to something of interest, etc.). My philosophy is to find potential problems with recalculation while sitting at my desk, rather than on the side of the road astride my bike.