BaseCamp 4.2.1 is available

There is a bug in.
By arrow straight on State in the text, to cycle, while a motor set.

What in the world does the above mean?

This is what you get when you use Google Translate...
What it means is this:
"I found a bug: In the list of route directions the description next to a straight arrow contains 'Cycle to' where it should be 'Ride to' since the Motorcycle profile was selected."

This is in the Dutch version. The original text was "Er zit nog een bug in. Bij de pijl rechtdoor staat in de tekst,fietst naar,terwijl een motor ingesteld staat."

I have been experimenting with the new BaseCamp "feature" that allows you to switch to another database, but it does not work like I would expect. Some of my experiments almost caused me to experience a coronary when BaseCamp began to unexpectedly crash during the restarts, and without an obvious way to fix the problem (I stumbled upon one), while another experiment failure almost resulted in the loss of my entire working database (yes, I had a backup, but BaseCamp kept failing during the restoration – I stumbled upon another fix). Anyway, if anyone decides to experiment with this feature, proceed with caution.

As you know, the default location for Win-BC to store it's database is C:\Users\%USER%\AppData\Roaming\GARMIN\BaseCamp (where %USER% is the user's user name).

I decided to have BaseCamp create an alternate database (Edit -> Options -> General -> Database Options). I selected the Plus icon, typed a new database name (in my case, Tracks Archive), typed in the default path for BaseCamp's databases (C:\Users\%USER%\AppData\Roaming\GARMIN\BaseCamp, with my actual username), and created the database (supposedly). Switching to that database (the arrow icon) and restarting as instructed yielded nothing – BaseCamp restarted and displayed my default database, but thought it was the "Tracks Archive" when I rechecked the setting under Edit -> Options -> General. Changing back to the default database and restarting returned me to the default database. A search of all folders within the default database location did not locate any newly created folders or files.

Redoing this process, but using the C:\Users\%USER%\AppData\Roaming\GARMIN\BaseCamp\Database pathname yielded a different result. This time BaseCamp successfully created a new series of folders within the C:\Users\%USER%\AppData\Roaming\GARMIN\BaseCamp\Database folder. Within the Database folder was a new folder called "Database," which contained a "4.2" folder, which in turn contained all the normal folders and files associated with a BaseCamp database. The new "alternate" database file was still called "AllData.gdb" and was, of course, empty (no data). Swapping back to the default database was successful.

At this point, I decided to try creating a new, alternate database on another drive. I went through the same process, but for a new drive and folder location. BaseCamp failed during the database creation process and crashed. Repeated restarts of BaseCamp resulted in further crashes. Examination of the new drive/folder location found that the "Database" folder had been created, but none of the subfolders and files. I was able to resolve the BaseCamp crashing problem by copying a set of the subfolders and files to the new location, which then allowed BaseCamp to restart.

I am continuing to experiment with the new Alternate Database feature, but thus far, it does not behave as I would have expected. A bit of documentation from Garmin, on how this is supposed to function, would be very helpful.

I'd forgotten about this (don't use BC much). I've been intending to move the BC database on two of my machines (could've used hard-links but...).

Anyway I just moved the entire BaseCamp folder in

C:\Users\%USER%\AppData\Roaming\Garmin

to another drive/path, changed the preferences, and restarted BC. It worked just fine (no crash). My database (My Collection) worked as did my Birdseye images. However the following folder is still created in my user profile and not in the new pathname.

C:\Users\%USER%\AppData\Roaming\Garmin\BaseCamp\SavedSearches

I've yet to try this on my XP machine where there are two copies of my Birdseye images (in two user profiles) etc needlessly using up HD space.

PS: I long ago changed the default location of files in MapSource to a different drive/path.

I'd forgotten about this (don't use BC much). I've been intending to move the BC database on two of my machines (could've used hard-links but...).

Anyway I just moved the entire BaseCamp folder in

C:\Users\%USER%\AppData\Roaming\Garmin

to another drive/path, changed the preferences, and restarted BC. It worked just fine (no crash). My database (My Collection) worked as did my Birdseye images. However the following folder is still created in my user profile and not in the new pathname.

C:\Users\%USER%\AppData\Roaming\Garmin\BaseCamp\SavedSearches

I've yet to try this on my XP machine where there are two copies of my Birdseye images (in two user profiles) etc needlessly using up HD space.

PS: I long ago changed the default location of files in MapSource to a different drive/path.

Yes, if you don't use BaseCamp to do the "move" or use another database all works fine. But, most users aren't tech-users and don't have a clue how to do that. Which would be the reason to have a very easy to use feature. Unfortunately, this feature in Win-BC is not intuitive nor does it work. I just tried to not only use another database and had the same experience as Mr. Murray, I also tried to do a Restore and again Win-BC crashed and would not accept the new DB without a reboot. Really poor form.

I sure hope these things get fixed before I present BaseCamp v4.2.x to the BMW MOA Rally in three weeks.

I decided to have BaseCamp create an alternate database (Edit -> Options -> General -> Database Options). I selected the Plus icon, typed a new database name (in my case, Tracks Archive), typed in the default path for BaseCamp's databases (C:\Users\%USER%\AppData\Roaming\GARMIN\BaseCamp, with my actual username), and created the database (supposedly). Switching to that database (the arrow icon) and restarting as instructed yielded nothing – BaseCamp restarted and displayed my default database, but thought it was the "Tracks Archive" when I rechecked the setting under Edit -> Options -> General. Changing back to the default database and restarting returned me to the default database. A search of all folders within the default database location did not locate any newly created folders or files.

I am a bit puzzled why would you create a new database exactly where the old one was? You are just setting yourself up for trouble here. We better add some checking that prevents you from doing that because (as you have experienced) all kinds of strange things can happen if you do.

However the following folder is still created in my user profile and not in the new pathname.

C:\Users\%USER%\AppData\Roaming\Garmin\BaseCamp\SavedSearches

Thanks for letting us know. We'll check this out.

I am a bit puzzled why would you create a new database exactly where the old one was? You are just setting yourself up for trouble here. We better add some checking that prevents you from doing that because (as you have experienced) all kinds of strange things can happen if you do.

I'm completely puzzled. I have a Dropbox location that has four "basecamp.bclibrary" databases in it. Are you suggest that Win-BC cannot create another database there and/or read from that location either of those library's? Which by the way so far it can't - crashes every time.

Just to be clear Mac-BC had no problem creating library's to or reading from that location.

OK, I just reread the release log;

• Added support for changing the location of BaseCamp's database
  
  

So, based upon your puzzlement I take that to mean Win-BC does not support multiple Library's in the same location?

OK, I just reread the release log;

• Added support for changing the location of BaseCamp's database
  

So, based upon your puzzlement I take that to mean Win-BC does not support multiple Library's in the same location?

Great observation, Dan. I never thought about re-checking the release log. It now seems clear that the Database feature is intended to allow the database to be relocated (i.e., an alternate database location) rather than the ability to create and use an alternate database. This explains why the new database retains the filename of AllData.gdb. It is a shame, since so many Win BC users have been asking for the ability to use multiple databases.