I would have sworn I wrote about this in the past, but when a member wrote in this week asking about having their Toolkit database shared across two computers, I could not for the life of me find a write up. With that in mind, I've put together some steps on how this can be done. The steps below do require some familiarity and comfort with navigating around Windows, but if you have more than one computer, and don't enjoy swapping files between two copies of Toolkit, this could be a very useful undertaking.
First, the basic steps:
1. Choose whichever copy of Toolkit has the primary library.
2. Copy that library over to a Drop Box folder.
3. Go to the secondary copy, and tell it to use the file on Drop Box.
Note: you won't lose any stocks that were in the original libraries; the secondary copy of Toolkit will simply start using the database from the primary copy instead of its own. If you have stocks in the secondary copy that aren't in the primary one, you should go to File > Export in the secondary copy, and make individual exports of those stocks.
This may be obvious, but if you don't already have Drop Box set up on both computers, go out to www.dropbox.com and get things set up on both computers.
Also, make sure you have the Library menu enabled on both copies of Toolkit. This is turned off by default, so here's a quick how-to on making sure it's active:
Select Preferences from the Options menu.
On the Preferences window, select the General tab.
From the check-boxes there, make sure that "Enable Advanced Library Options" is selected.
Click the OK button at the bottom left-hand corner of the window.
Setting the primary copy to use Drop Box
In whichever is the primary copy of Toolkit, go to the Library menu, and select Library Manager.
From the options that come up, select the 2nd one, for saving a copy of the current library.
Toolkit will default to naming the file with the current date, so that you will see a file name like TK130607.MDB
It's up to you if you want to change the name or not; just be sure to make note of the name you use.
In the window that comes up, navigate to the public folder of your Drop Box.
Drop Box usually installs a shortcut onto the desktop, so the most common steps for this will be:
Click Desktop on the left hand side of the Save Toolkit Library window.
Double-click the Drop Box icon.
Double-click the Public folder.
Click the Save button (sometimes this will show up as Open instead of Save)
Toolkit will return to the Library manager window, close this, and then close Toolkit as well.
You'll want to check that the file has been uploaded to the Drop Box server. To do this, find your Drop Box folder, open it up, and check in the Public folder.
If the file you saved has a small green and white check-mark next to it, then the file is all set on the primary computer. If you see a small blue arrow symbol, that means the file is copying over to the Drop Box server; this usually shouldn't take more than a minute or so.
With this done, go to the secondary computer, and check your Public Drop Box folder there; depending on the speed of your internet connection, and the size of the database, the file may take a minute or two before it shows up.
Once you have confirmed that the file has shown up, open your copy of Toolkit on the secondary computer.
If you haven't done so already, make sure to follow the steps above to enable the Library menu.
Go to the Library menu, and select Library Manager.
From the options that come up, select the 1st one, for opening a previously created library.
In the window that comes up, navigate to the Public folder in your Drop Box; this should be similar to how you got to the Public folder on the primary computer.
Double-click on the Toolkit file, and then click Close on the Library manager window in Toolkit.
Your secondary copy of Toolkit will now be using the same library as the primary copy.
As a word of warning, I suggest to make sure that you do not have Toolkit open on both computers at the same time, so there is no confusion in the program about which copy of Toolkit will be writing/updating the database.