I have a new database on one Mac which I want to use on another Mac.
On the first Mac I sync the DB to a (Dropbox) sync store. On the second Mac the DB appears in the sync store under the Remote heading. So far so good.
But when I right click the DB on the second Mac the “Import Database” menu entry is always greyed out:
What to do? - Thanks for pointers!
Is this sync store already used by other databases? Maybe one of them is currently synchronized and then it’s not possible to perform other operations on the sync store.
Something like this it must have been: I tried the next morning and I could import the database. So I’m happy now.
Side thought: The greyed-out indicator is very elegant and minimal, but rather not helpful in a case like this…
Did you check the Activity pane/panel for any tasks?
No, I didn’t - but I will next time. 
Hello, I would just like to clarify what is meant by the comment “Is this sync store already used by other databases? Maybe one of them is currently synchronized…”.
I sometimes also have difficulty uploading a remote database (from Dropbox). Is this a typo, and was the intended answer that if any database on any computer that is open and running DT is in the process of synching, then until all synching has ceased, it will not be possible to upload a database to another computer? Would it therefore be true to say that, if proposing to upload several databases, it would be best first to close DT on other computers, or at least to untick the syncbase temporarily on those other computers?
If a database is actively syncing on the machine you’re on, you can’t do certain things like importing a new database from the sync location.
then until all synching has ceased, it will not be possible to upload a database to another computer?
You’re not going to “upload a database to another computer” unless you were using a Bonjour sync. This is important to understand and keep in mind. If you are using a Dropbox sync, then where are you syncing? Not to another of your Macs. Logically, you are syncing to Dropbox’s servers. What happens to that sync data depends on what happens on the other devices.
Would it therefore be true to say that, if proposing to upload several databases, it would be best first to close DT on other computers, or at least to untick the syncbase temporarily on those other computers?
No, this would not be true.
Enable the databases you want to sync and let them sync when its their turn.
Thanks Bluefrog. I am not having any issue with syncing databases, which works well for me no matter how many are open. This is not a question about synching. The issue is that I have about 40 databases, but only about 20 of them are in regular use. So typically the 20 regular databases exist locally on all three of my Macs. The remaining databases are on the syncbase (and of course also backed up on removable disks). When I want to access a reserve database I therefore upload it from the “remote” section of the syncbase. However, it is quite hard to do. Either the database in question is grayed out, or if not, it just pings when I try to upload. However, if I persist long enough, I do get to upload it. Obviously, something blocks the upload most of the time. If I see no syncing activity on the mac being uploaded to, then it would seem logical that one of the other two macs might be causing the problem because they are running through a sync routine (even if there is nothing that needs syncing). But I think you are saying that the activity of the other two macs does not influence the ability of the active mac to upload a remote database? Or do I misunderstand you on that point? Perhaps having 20 database all syncing from three machines is keeping the system too busy? Am I better to have more than one syncbase in Dropbox so as to spread the load a bit?
The remaining databases are on the syncbase (and of course also backed up on removable disks). When I want to access a reserve database I therefore upload it from the “remote” section of the syncbase.
So are you deleting the local copies orf the database when you’re done with it?
Yes, as you say, especially on my laptop where there is less space. I realise it begs the underlying question which is the best strategy for dealing with large numbers of databases accumulated over 15 years of using DT. At least half are for reference and archive purposes only, and will not be changed so that there is probably little benefit to putting them on the Dropbox syncbase I created. I have massive overcapacity on Dropbox. Might it be sensible to have a second syncbase for these, or even (if this is not total heresy) to copy them to Dropbox outside of a syncbase? (Of course, they are also backed up elsewhere, but I don’t carry those backups around with me or have them by my computers).
If only Macs are concerned (no iOS devices), you might want to store those databases on a portable SSD and bring it with you. Plug the SSD into any one of your Mac, and you have instant access to all those databases, without having to wait for sync.
Drawback: you must buy the PSSD, which adds ~100 grams (the Samsung T7 Shield weighs 98g) to your pouch or pocket.
Yes, I do agree this makes good sense as a strategy, and I do do this to some extent already.
At the moment, I find it quite hard to clean unwanted databases on the existing single Dropbox hosted synchbase, and also hard to upload “remote” databases from a synchbase.
I think that my original question was wrongly asked. I should have been asking whether having 50GB of data on 40 databases on one synchbase, whilst also having three macs open all running through synch routines, is perhaps overstretching the system by blocking me whenever one of the macs is checking whether there is anything to sync.
It would seem to me that I would maybe find things work better if the synchbase was smaller (and I perhaps had several synchbases). Also, maybe it would help always to close down DT on those machines currently not being used. However, opening and then closing 20 active database each time I use a machine is a bit of a hassle since on a daily basis I use all three macs.
Workspaces remember which databases are open so once you set up a collection of related databases that you would need on any machine, invoking that workspace would open them all up.
Someone else would have to answer if there was a way to copy workspaces from computer to computer.
Now I admit I haven’t tried this next suggestion but…
would invoking a workspace with only one database open then close all the open databases?
Gonna try that when I get to my main machine.
It would seem to me that I would maybe find things work better if the synchbase was smaller (and I perhaps had several synchbases).
I would strongly try to dissuade you from your current practice. It is incredibly inefficient and you are using sync in a way it’s not intended. What do you do if Dropbox or your network is down? And you’re nowhere near your backups, whever they are? @meowky is quite correct in the suggestion of getting a portable external hard drive and putting your databases on it, if space is at a premium on your internal drive.
OK, accepted. Thanks. Do you have any comment on my question about how many databases can comfortably reside on one synchbase, and whether it is better to have more than one synchbase if there are large numbers of databases? There is still the issue that when I create a database on one mac, I need to upload it to another from the remote portion of the synchbase, which is not easy. Also, that when I have created an ad hoc database that is on the synchbase, it is hard later to “clean” it from the synchbase when it is no longer needed. Do synchbases get less easy to operate when they get too big, and is it better to have more than one synchbase perhaps to ease this problem? Also, does it make any difference to the process whether or not all macs are open with DT given that something (probably synchs) seems to be interrupting the process of downloading from the remote portion of the synchbase, or cleaning the synchbase?
I never thought of the Workspaces method. I must give it a try! Perhaps workspaces are for me a neglected DT asset… (of which there are many)
