What is wrong in asking this question again.
What is wrong is that you were told that the available technology doesn't work that well for the kind of synchronization you want to do. Further, as fast as technology is changing, it ain't changing that fast that you'd get a better answer in less than a month.
You may not see it this way, but playing the "shop around for a better answer" game makes it look like you don't trust us. We are telling you things that we believe WILL work and things that WON'T work. So... what part is unclear?
As to repeatedly asking the same question over and over again, it appears that we have failed to communicate with YOU that we heard you the first time you asked this same question. If you and we are communicating that poorly, why bother to ask in the first place? (Well... OK, second or third place by now).
I'm not trying to disparage your problem. You have been told that a terminal services solution of some kind is the best choice for WAN connectivity. You have been told that cloud services might not be reliable enough because of the protocol that Access uses. The Server Message Block (SMB) protocols are very sensitive to lost connections and can leave things dangling in the worst possible sense of that phrase. SMB over a shaky connection is a guarantee of database corruption waiting to happen.
I have no doubt of the legitimacy of your problem. It has been faced by many of us. We have tried stuff and found that for flaky, shaky connections, SMB is NOT the answer. TSS or RDP or some other remote terminal solution is your best choice.
If I sound a bit brusque, it is only because we need to impress on you that we HAVE heard you. Now YOU need to hear US.
