This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multiple DataBase in BaseCamp

I have noticed that working on large data base increases the risk of crashes. May be it's just a feeling but for sure corrupting a large amount off data is more frustrating than damaging a small DB.
So I would appreciate suggestion about working with multiple DataBase.
I have learned trough "preferences" that I can select a DataBase, create a new one etc, but I am not sure to obtain the expected results. How merge occurs all these kind of things.
My goal is to build a large DB (60000 POIs), while working on smaller dataset. When happy with my small sets I want to merge them and deal only with POIs shared among smaller sets.
If you you have the know how to manipulate BC DataBase your help will appreciated.
  • If I understand what you are trying to accomplish, I would suggest creating 10 or so databases using Preferences->Advanced->New Library. Once you are happy with the small libraries, you'll have to export GPX and import them into your master library.
  • ...you'll have to export GPX and import them into your master library.
    Note that GPX files do NOT support folders or lists. They are "flat". Thus when importing GPX file(s) one has to recreate any folders/lists in BC and manually move/copy data to them.

    To my knowledge there is no easy way to merge (or split) BC databases.
  • Thanks for your suggestion. I have one gpx file by list and it's OK like that.
    At the moment I have two instances of BC one in 2.4 (prod like) in french an another with BC in 4.3 (Dev like) in english. Using GPX to exchange data seems to work fine.
  • preferences?

    If I understand what you are trying to accomplish, I would suggest creating 10 or so databases using Preferences->Advanced->New Library. Once you are happy with the small libraries, you'll have to export GPX and import them into your master library.


    Where do you see "preferences"?
    Thanks..
  • According to my experience with BC, there is no easy way to merge two databases and I would really discourage of using the database format (*.gdb) at all. You can export to the gdb-format, but you cannot import without loosing all structure (folders, lists). That's almost useless for big databases. You would have to export every single list seperately. After re-importing all these lists to another DB you will need to manually rearrange your desired folder structure. That's a big mess! Unfortunately, there is no easy save and open option for databases included in BC.

    I have tried to find a way on how to work with a BC DB that is stored in the cloud (OneDrive) and can be accessed by all my computers remotely and consecutively. The only way of working that seems to be feasible for me is to manually backup the DB after every single modification and to store that backup file back to the cloud. First step with a different computer is then to restore the backup file and after work is completed to backup again. Following this inconvenient procedure allows at least to keep the structure. Nevertheless, big DBs take some time for backup and restoring, unfortunately.

  • As you've replied to an 8 year old thread I'm closing it as you don't appear to have a question. If you do please start a new thread. Thanks