I have updated to Basecamp3.2.1.I ended up losing my Library under My Collection.And It was replaced by a recovered Birdseye Imagery List( I didn`t lose it to begin with.)Then I started to get a Warning"Cannot load the following Areas".Under which was listed Birdseye Imagery and KML Data.Under that was another" Warning Data could be lost"then it ask,"Do you want to attempt to fix the Data?".Then it gives you the option to Fix or Cancel.And also the new basecamp version no longer shows how many Waypoints,Routes,Tracks,Birdseye Imagery,Garmin Custom Maps,Geocaches and Geo-Tagged Photos you have .This was a very useful feature.It was at the bottom of Basecamp on a pull up menu.Now there is no longer a pull up menu.Please bring it Back!.
I have this exact same problem, so I restored my program files and user appdata from backup, and then I restored the backup file I made and so I am on 3.1.3 with all my data. However, now when I try to install 3.2.1. is says it installs, then launches 3.1.3 and wants to install 3.2.1 again, over and over.
I have updated to Basecamp3.2.1.I ended up losing my Library under My Collection.And It was replaced by a recovered Birdseye Imagery List( I didn`t lose it to begin with.)Then I started to get a Warning"Cannot load the following Areas".Under which was listed Birdseye Imagery and KML Data.Under that was another" Warning Data could be lost"then it ask,"Do you want to attempt to fix the Data?".Then it gives you the option to Fix or Cancel.And also the new basecamp version no longer shows how many Waypoints,Routes,Tracks,Birdseye Imagery,Garmin Custom Maps,Geocaches and Geo-Tagged Photos you have .This was a very useful feature.It was at the bottom of Basecamp on a pull up menu.Now there is no longer a pull up menu.Please bring it Back!.
If you're trying to install 3.2.1 and get rid of 3.1.3:
First, uninstall any and all BaseCamp versions from the Windows installer. That's where the uninstall fails. It will remove everything from the program files folder that is a subfolder, but leave all the files in the root, which ironically, is where all the real program data is.
For me, I had to go into program files\garmin\basecamp and wipe that folder out completely. Then go into C:\Users\[your account]\AppData\Roaming\Garmin\BaseCamp\Database and wipe out the 3.2 folder, keeping 3.1.
That worked, but after spending more time adding waypoints and stuff, I closed 3.2.1 and later opened it. Same error about wanting to fix the data... and when I did, my collection was wiped out. Restore from backup to 3.1.3 and I'm leaving it alone for now. >sigh<
If you're trying to install 3.2.1 and get rid of 3.1.3:
First, uninstall any and all BaseCamp versions from the Windows installer. That's where the uninstall fails. It will remove everything from the program files folder that is a subfolder, but leave all the files in the root, which ironically, is where all the real program data is.
For me, I had to go into program files\garmin\basecamp and wipe that folder out completely. Then go into C:\Users\[your account]\AppData\Roaming\Garmin\BaseCamp\Database and wipe out the 3.2 folder, keeping 3.1.
Okay, here is some more info. I was able to install BC 3.1.3 on my desktop computer (the upgrade to 3.2 was on my laptop) and transfer the 3.1 data files from my laptop to the desktop and got them working. I did a backup from 3.1 and restored the file into 3.2, all I get is a Birdseye Image item but none of my previous data. I can provide the backup file if you like.
More info. I was able to copy the database files from the 3.1 directory into the 3.2 directory and get my lists back. However, they randomly become unuseable by the software. Short story I do all of my loads from the 450t into 3.1 arrange the data the close and copy the 3.1 databases over to the 3.2 folders and perform a backup. That way when 3.2 messes up the data files I can restore from the BU.
Development is aware of the data corruption issue and says they're working on a fix. In my opinion though, 3.2.1 is not a usable version at all because of all the corrupt data issues. I'm on 3.1.3 until they thoroughly test this thing.
