Mac/Windows Software

Basecamp Windows User determinable database location

User determinable database location

Former Member over 13 years ago

I wonder if Garmin, in a future update to Basecamp, will allow the end user to determine where the database is to be located. Unless I'm wrong, the installation of BC defaults the database to the 'C' drive which is the last place that I would want it or indeed any data files.
Other database orientated applications that I regularly use also default to the 'C' drive but also allow me to relocate it some place else e.g. my 'D' drive. Once the applications start up, a pop-up advises that the database file cannot be located and gives me the option to manually locate. From then on, the application uses that database location.
Having this ability would allow me (and I feel sure others) to more easily backup the database file along with other data as part of their regular backup routine. Yes I am aware that it is possible to backup the BC database file from within the application itself but this simply adds one more step to a regular backup routine. I am surprised that Garmin as application developers haven't adopted this as standard as most users whose data is valuable know that it is not good practice to have applications and data on the one drive.
Please Garmin, consider making the location of the database file user definable. :) Thanks.

0 Former Member over 13 years ago

I support this idea

0 Former Member over 13 years ago

Probably THE most requested feature since the announcement of MapSource's demise....
It is possible, or so I'm told, using some special tricks inside Windows.
You might hunt around in these forums and turn it up... but if Garmin would implement it within the program itself, such shenanigans would be unnecessary.

0 Former Member over 13 years ago

Unless I'm wrong, the installation of BC defaults the database to the 'C' drive which is the last place that I would want it or indeed any data files.

Please Garmin, consider making the location of the database file user definable. :) Thanks.

I agree

0 Former Member over 13 years ago

Well it would be nice if TALAGAR the Desktop App Developer, who seems a bit choosy when it comes to deciding in which posts to make comments, had posted something here. Oh well. :(

0 SUSSAMB over 13 years ago

Give him time ... he's a busy man :)

0 Former Member over 13 years ago

I guess I will have to answer now after being called out like that...

I generally try to answer posts that aren't already sufficiently answered by a community member. But I don't always meet that goal.

Back to the topic at hand: we have a case for this, but it's not high priority. We certainly don't want another pop-up dialog at start-up for this, and we probably don't want to expose this to the average user. So this would be a setting somewhere pretty deep in the options dialog. I don't believe the average user(like the ones that would never dream of visiting this forum) particularly cares where the data is stored. One of the reasons for BaseCamp's existence is to get away from file micro-management. The idea is to just launch the program and the data is there.

But I don't mean to discard the proposal. There is obvious interest for this feature, and I certainly understand that it could be very useful. So we'll see what we can do. But glancing at the stack of things we already have on our plates, I just can't promise that this will happen very soon.

0 Former Member over 13 years ago

We certainly don't want another pop-up dialog at start-up for this, and we probably don't want to expose this to the average user.

Not sure why you think a pop-up is necessary or that something would need to buried deep within the Options settings. Adobe Photoshop Lightroom is one of the other database applications that I use. The database file (called lrcat in this instance) is installed by default where Adobe have determined it should go. However, if the user moves it to another location, Lightroom will on start-up advice that the database file cannot be located, do you want to locate it yourself or start another one. In the instance that the user chooses to locate it, Lightroom will continue to use that file at all other start-ups. This is the only instance of a pop-up appearing so if Garmin were to adopt this sort of approach then you'd not only be satisfying those who want the ability to choose where they locate the database file but also yourself as your so-called average user will be non the wiser.

Thanks for replying though and good to read that the proposal isn't to be totally discarded.

0 Former Member over 13 years ago

We certainly don't want another pop-up dialog at start-up for this, and we probably don't want to expose this to the average user.

It would not have to be at start up. Another solution would be to offer the option of choosing where the data are stored on installation. I believe back-up is important and if this can be integrated with one's routine system back-up, there is less chance of it being forgotten.

0 Former Member over 13 years ago

Best Solution -- IMO

It would not have to be at start up. Another solution would be to offer the option of choosing where the data are stored on installation. I believe back-up is important and if this can be integrated with one's routine system back-up, there is less chance of it being forgotten.

I think this is the best solution.

I use Ghost to back up an image of my "C" drive. Because I often try out new program I back up my C drive each night. I restore my "C" drive about 6 to 10 times a year. All my other data is stored on my "F" drive. The F drive is backup up on a routine time frame. Now when I restore my C drive -- which is always a full restore most often from a backup that is 2 to 3 months old (before I tried out the new programs), I must go into a different restore (file only restore) to restore my BC data files form a restore that is only a day old.

0 Former Member over 13 years ago

Oh! and speaking of pop-up, I keep ticking for the annoying request to participate in product improvement not to appear on startup, but it persists in doing so!