When MapSource users import their old gdb files into BaseCamp and find every Waypoint must have a unique name they don't like it. The first time I saw waypoints named Home, Home1, Home2,...,Home5, I was concerned. I tried repairing this by selecting the most best version of this waypoint and replacing the other 5 with the best version. Home4 isn't used in any lists, yet I cannot delete it in BaseCamp. [Bug Report: If you use the "X" in a waypoint properties Lists tab, that waypoint becomes undeletable.] That is frustrating to not have an explanation for no delete available for an unused POI. While I understand how to reduce this waypoint reassigning to a minimum, it is a lot of extra effort.
There are also mysteries in the Map database where sometimes making a waypoint out of a map POI results in the name being changed to include the trailing number and other times not. Whatever the reason for this discrepancy should be changed for consistency. Why do we make waypoints out of map POIs? Because the map POIs are many times innacurate as to location and don't include URL references and user entered descriptions.
When a MapSource user exports one of their lists to a gdb to look at it in MapSource or directly sends it to their GPS and finds that many of their waypoints have been renamed with a number at the end of the names, this does not lead to acceptance of a database approach like BaseCamp. I'm guessing when I read someone's comment that BC "messed up" all their routes that it is a combination of this and a somewhat different routing algorithm.
Once the user has all their information in BC and resolves most all the name issues, going forward it is easier, as all waypoints in lists link back to the same database entry. If the location is refined and the user updates it, all lists using that waypoint are updated.
Maybe a tool in BC to resolve this would be useful, letting the user determine the waypoint of a numbered group to use by displaying all the unique data. The user chooses the the default and replace all the numbered ones by this default, unnumbered one.
A separate feedback comment is that I find MapSource routing, is easier to use than BaseCamp. The sticky location caption bubbles don't change frequently enough when moving the mouse looking for an address and are not present in the rubberband via point Insert Tool. Consider a review of the MS and BC processes of route design to see where effectiveness improvements can be made.
