Home Forums Discussions Problems Sync problems

We use a server for the main database in our office. We do calls in nursing homes so practitioners take a tablet which is "synced to go" before leaving and synced back upon return.
The tablets, even after being synced back and in our office, remain using their own database, rather than switching back to the server automatically which would be logical.
Also, if messages and appointments are read or deleted on a tablet but not on the server database, as soon as a "sync" takes place they are back on the tablet. The sync function is necessary in our practice but definitely needs some work.
I know that a warning about using sync was just issued and I hope it is cleaned up to address these issues in the update.

I was wondering if this issue had been addressed? We had the same problem, and stopped trying to use the sync function since we didn't really need it to work at the time. Now things in the office are clicking along, and it would be nice to be able to sync the tablets to take to the hospital and nursing home but I hesitate to make changes when everything is currently working so well.

Thanks . . .

You want to synch the tablet every time you take it out of the office, and then synch it back to the main database when you come back into the office with the tablet. Once you have synched it to the main, you need to reset the path back to the main computer if you wish to do charting on the tablet while in the office. If you do not reset the path to the main, and run the first option of the synch again to take the tablet off site to the nursing home you will overwrite your information on the tablet that you were imputing while in the office with the path set to the tablet.

That is why when you delete a message on the tablet, and then synch with the first option the messages come back in your messages. The first option just overwrites what is on the tablet with the current data on the main computer. It does not add to what is on the tablet. The second option adds what is on the tablet to the main.

Thanks! I did not realize we needed to reset the path upon return.

Tech support:

How about making AC smart enough to realize that when the tablet is synched, and connected to the server, we want to continue to use it with the server?

We only want it to have "it's own" database when we again sync to go away?

If the program was smart enough to do that on it's own that would be great. Please forward your idea through recommended improvements please. I understand how difficult the Synch process can be, and for now you have to remember to reset the path.

-Eric