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

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!

Are you using 4.0.5? That seems to work for me, it should be ticked automatically. In order for the window not to reappear the check-box must be checked, no un-checked. (Just to cover all the bases.)

Is anyone else seeing this?

0 Former Member over 13 years ago

Provide user choice of install directory and data directory

There is another thread asking for support of multiple databases. That is, to allow the user (perhaps under File|New) to create a new named database and open different ones whenever s/he wants (e.g. File|Open).
That could certainly be combined with allowing the user to specify the directory location in which the BC database (and other related files) are to be stored.
Such features are common in well-known software (i.e. from Intuit, Adobe, ...), do not confuse 'non-techie' users, and are appreciated by more savvy users who want to insure their data are backed up.

So, in summary ....

At install time:
1. indicate default install directory; let user pick a different location if desired.
2. indicate default data directory; let the user pick a different location if desired.

In program at run time:
3. provide File|New to let the user create a new named database
4. provide File|Open to let the user switch between databases
5. provide in Options the ability for the user to change the data directory

-ceej

0 Former Member over 13 years ago

Options 3&4 are really all we need.

There is another thread asking for support of multiple databases. That is, to allow the user (perhaps under File|New) to create a new named database and open different ones whenever s/he wants (e.g. File|Open).
That could certainly be combined with allowing the user to specify the directory location in which the BC database (and other related files) are to be stored.
Such features are common in well-known software (i.e. from Intuit, Adobe, ...), do not confuse 'non-techie' users, and are appreciated by more savvy users who want to insure their data are backed up.

So, in summary ....

At install time:
1. indicate default install directory; let user pick a different location if desired.
2. indicate default data directory; let the user pick a different location if desired.

In program at run time:
3. provide File|New to let the user create a new named database
4. provide File|Open to let the user switch between databases
5. provide in Options the ability for the user to change the data directory

-ceej

0 Former Member over 13 years ago

So, in summary ....

In program at run time:
3. provide File|New to let the user create a new named database
4. provide File|Open to let the user switch between databases
5. provide in Options the ability for the user to change the data directory

-ceej

Can't you do this by backing up the database with a unique name, deleting everything then creating a new database with the new and separate data (i.e. Western US and Eastern US), then simply use the restore command to switch between the two? I've never tried it, but I don't see why backup/restore can't be used in this fashion.

0 Former Member over 13 years ago

Options 3&4 are really all we need.

I beg to differ; and so does the OP. A lot of people prefer to have control over the location of their data files. Some (as the OP and I) have an additional hard drive as D:/ where we put most all data files (for easy backup among other things).

In any case, it is commonly offered as part of the software installation and IMHO appreciated and valuable.
-ceej

0 Former Member over 13 years ago

Can't you do this by backing up the database with a unique name, deleting everything then creating a new database with the new and separate data (i.e. Western US and Eastern US), then simply use the restore command to switch between the two? I've never tried it, but I don't see why backup/restore can't be used in this fashion.

Yes, I am sure that is a workaround that would work. But it is not hard to implement direct support in the software and makes the user operations much simpler and less prone to error. I assume that it will come in time.
-ceej

PS
As a good example, look at Intuit's Quicken product.

0 Former Member over 13 years ago

I beg to differ; and so does the OP. A lot of people prefer to have control over the location of their data files. Some (as the OP and I) have an additional hard drive as D:/ where we put most all data files (for easy backup among other things).

In any case, it is commonly offered as part of the software installation and IMHO appreciated and valuable.
-ceej

Well, then perhaps I missed the nuances of all the other items listed. And as you mention, Quicken is a great example. In Quicken, you specify what file to open, and it *assumes* you want all the auxiliary files in the same dir. By my saying 3&4 are really all that is needed, I'm suggesting that if Garmin implemented simply that, they would still meet their goal of staying simple for everyone, while allowing some of us the extra control we want:

By default, basecamp could store data where ever it does today.
If I had the option of saving/opening a db file, I should be able to specify any of the following examples:
(a USB or stick drive) N:\data\basecamp\bc_data_now.bcdb
(a network share) \\DiskServer1\shared_data\Basecamp\my_database.bcdb
(a dropbox point) C:\Users\me\Desktop\Dropbox\data\BasecampDB.bcdb
etc etc,

ETA: I use quicken, and on my tower PC save the DB file to C:\QuickenData\QData_Now.qdf, which I share to my laptops. On my laptops, I open \\towerPC\QuickenData\QData_Now.qdf Also, the tower automatically backs up C:\QuickenData\* to a network-attached drive dedicated solely for backups.

0 Former Member over 13 years ago

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.

I support the proposal, please don't discard it.
I'm sure it's pretty simple to implement, an extra option in an XML file and a few more controls to be displayed in options window?

Thanks.

0 DaveA_ over 13 years ago

+1

There must be some ability to shuffle items on the plate. This would be a very welcome feature. Certainly above "adventures", but that's just me.