The image above shows two databases. The ‘evidentia‘ database is currently open, and because it is local, it is displayed in black text. The second database, ‘ThompsonHayward‘, was created on another device, and this device does not have a copy, so it is displayed in blue.
Now the current device KNOWS about ‘ThompsonHayward‘ because it exists on Dropbox, and Evidentia has synchronized the list of available databases.
So why doesn’t the device have its own copy?
The short answer is because the user has never opened the database on this machine. As soon as the user opens the ‘ThompsonHayward‘ database on this machine, Evidentia will keep the copy on BOTH machines in synch.
Why not be proactive and synch to the local machine just in case the user wants to work with that file later? There are several reasons.
- Not all devices have unlimited storage space. Evidentia tries to limit its use of storage space to the work actually being performed on the device.
- Users may work with different databases on different devices, and not need or want a copy on all their devices. If they do, they can simply open up the remote database to insure a local copy
- For performance reasons, Evidentia & Dropbox both have the philosophy of not moving files around unless the user requests it – the user is in control.
So if you see a database in blue, rest assured that it is not taking up any unnecessary space on your device, but a copy DOES exist on Dropbox. If you want to work with it on your current device, just open it and Evidentia will do the rest!