In Basecamp release 4.2.1 (I think) a function for changing the location of the database was added. Where do I find that option? Does this change the location for installed maps as well as routes and tracks etc.?
I have both pointed to the folder:
Shared Database
...\Documents\Garmin\Shared Database\Database\4.1
I confirmed the path on both computers.
I deleted everything in the folder "Shared Database" from my laptop.
I confirmed that Basecamp showed no data on either computer.
On my laptop, I restored the db.
On my laptop, I opened BC and confirmed that the data was correct.
On my PC, I opened Basecamp and it showed the data correctly.
I deleted a test list using my laptop.
I opened BC back up on my PC and the list was unaffected.
Something isn't working like I expected if it were truly sharing the same db.
If you are sure that this should keep both computers' information in synch, then I'm scratching my head trying to figure out what I'm missing.
I think it's something to do with permissions on the shared folder.
That was going to be my next suggestion.
PS: Note that there are two types of permissions you have to worry about: the ones on the local (HD) files and folders and the shared folder permissions. They are independent.
I'm not sure why it made a difference, but when I mapped the folder as a drive, it started working great!
You are correct about it only supporting one session though. It seems that the session doesn't write the updates until it closes.
Thanks everyone for the help.
I'm not sure how long, if ever, it would have taken me to consider mapping the folder as a drive. It seems to have been the ticket, if not the problem.
I'm not sure why it made a difference, but when I mapped the folder as a drive, it started working great!
Well it can depend on how it was programmed (i.e. what API was used). That's why I suggested mapping to a drive letter. Fortunately that did the trick.
It seems that the session doesn't write the updates until it closes.
Well the BC database was never designed using a client/server (i.e. multiple user) model. The assumption is that BC and the database is on the same machine with only one instance of BC running at once. When BC is opened parts of the database are read into memory and when it closes changes are written back out.
Now BC doesn't seem to have any mechanism to prevent simultaneous accesses (e.g. a semaphore file) so you just have to be careful that one, and only one, instance of BC is accessing your shared database at once.
