I removed 2013 and started using 2010 again. I often solve this by including the version in the file name (this is a dev PC so I have about 7-8 versions of MapPoint Being able to identify map files without opening them would be useful though. Yes it is a pain, but I don't think it could be any other way. Wouldn't be able to to get down to a mere double. Even with some clever version compression you probably Has a complete set of the old format's road data! So yes, Streets&Trips 2013 could be written so that it could save to the previous two versions, but this would probably almost triple the road dataset. A new version cannot save to the old format unless it In theory, going backwards is even worse but it also adds some more fundamental problems: An old version cannot read the new version, because it can never know what future file formats will be like. More likely to have new/different roads, towns, zipcodes. Converting from one version to the next will introduce mis-placed pushpins/etc. This is why a file has to be "converted". Different versions of MapPoint / Streets&Trips have different data sets and road data networks.
0 Comments
Leave a Reply. |