We have a Timeslips Premium subscription and the desktop software is installed on one PC in the office that is used by our billing clerk to pull slips in from Timeslips Go to send out bills at the end of each month. We have two timekeepers, each of which signs-on to Timeslips Go to enter time. We have two distinct types of clients (Type 1 and Type 2) that we bill for the professional services we provide. The timekeepers enter slips for Type 1 clients into Database 1 and slips for Type 2 clients into Database 2. We have 2 licenses for Timeslips GO, one for each Timekeeper.
Our Problem: When we try to set up Timeslips GO, we get the token by signing in to Timeslips GO and then going to the PC referenced above and entering that token when asked to do so. At that time we have opened Timeslips on that PC and it opens with one or the other of the two Databases referenced above. We upload the client names, etc. to Timeslips GO. All works well. BUT - THEN - we close the Database used to set up and upload to Timeslips GO and open the other of the two databases we work with. Then we want to upload the clients from that database. This short-circuits the program. It reports it has a syncing problem. This tells me the program has been set up for the database first used, and when we switch to the other database, the program does not recognize the data there and it refuses to just co-mingle the databases. We don't seem to be able to generate two distinct tokens as referenced above. Each time we ask for a token, Timeslips GO gives the same token. So we can break the link with Timeslips Go for Database 1 and use the token to make a link with Database 2, and go on and on with that, but there does not seem to be any easy way to just set up Timeslips GO, and then switch from Database to Database and move right along.
Please see attached a redacted screen-shot of the screen that pops up on the PC referenced above, when we switch from one Database that is set up and working fine to the other Database. Now we can break the link with the Database that is working fine and then open the other Database and set it up and upload to it and all is well, but then, but then, if we switch to the other database, we get this same message that you see in the attached screen-shot.
What are we doing wrong and is there some fix for the problem described above?
If you read the error message in the attached, it could be understood to be communicating something like this: "Don't worry. Just add something to this new Database you just opened and then the "Transfer" box will light up green again, and when you click that, all these new names I don't recognize as having anything to do with what I'm being asked to sync will be uploaded, and we'll move right along." But we don't that that's what the error message really means and we don't want to waste time trying that imagined "fix" if it's not one.
Thanks so much in advance for any instruction, advice, help or work-arounds you all can provide.
P.S. Do we just need to get 2 more Timeslips GO licenses; the 2 we already have could set up accounts for Database 1; and the 2 more we would get would set up two more accounts to work for Database 2. Is that the fix? Surely not. Please tell us that is not how this was designed to work. That would mean we would have 4 Timeslips GO "accounts" instead of the 2 we currently have (one for each timekeeper-database users pair, given that we have 2 timekeepers and 2 databases we currently bill from)?
