Its file "C" which MUST be on dropbox.Įvery time "A" opens his. kdbx called "B" and is the ONLY computer every to open read/write file "B"įiles "A" and "B" might be on dropbox but thats essentially for crash/backup protection.īoth "A" and "B" have database "open" triggers which perform a two way record level sync with file "C". kdbx called "A" and is the ONLY computer every to open read/write file "A"Ĭomputer "B" uses a. Either way this is a bad situation.Ĭomputer "A" uses a. Or both parties will feel dropbox is not doing its thing and and getting changes over to all parites. Someone is going to to have their data entry lost Not matter what someone is going to be unhappy. Or dropbox did not deploy anything and "A" has its file and "B" has its and neither ever sees the other. kdbx will NOT contain both "A" and "B" the only thing drop box can do is one of: You user "A" and user "B" come back from lunch and open their. so whichever one is microsecondly more current will be the winner and pushed everywhere. The file has changed differently but there can be only one winner. Now dropbox does its thing and trys to deploy the most recent file to all computers. kdbx file name that filename is on dropbox.Įach then saves their changes and closes their.
0 Comments
Leave a Reply. |