| Subject | Re: Google Drive as a file sever (Why not to opt in for this) |
| From | Akshat Kapoor <akshat.kapoor@kapoorsons.in> |
| Date | Sat, 14 Sep 2019 17:30:48 +0530 |
| Newsgroups | dbase.getting-started |
On 14/09/2019 16:37, Mustansir Ghor wrote: > Hi to All > > Is this can be done. I would say Eureka. > > However my current approach to access file server is using VPN. Anybody can comment on its speed and stability. > If VPN is working then continue using it. Google drive is easy to install. You download and install it. It makes one directory on your computer as storage for Google drive folder. Anything in that folder or its sub folders are synchronised across devices as when network becomes available. You can configure your app to use this folder as your data folder. But the problem starts now At say 10:43 User A starts to edit a row. He saves the row but does not close the form. After multiple edits he closes the forms at 10:59. User has saved the info but since the rowset is active file is not closed. Till the file is open Google drive CANNOT upload it. At 10:50 some other user at a different location starts edit in a different row and closes the form at 10:58 Which VERSION of the file will Google retain. There is a conflict which cannot e resolved by anyone as no one can keep track of which row he has edited. I have not even considered Internet connection failure, which would complicate things even more. Now compare it with access over network. You only need to requery() and you have the latest data even if the other user has not closed the form. The chances of conflict are there but can be reduced to small percentage with planning. With Google drive you cannot even build a proper plan. So I with my experience of few years of using Google Drive for Backup would never recommend use of Google drive folder as a data folder for dBase app. Regards Akshat | |