RainLover
VIP From a land downunder
- Local time
- Today, 14:52
- Joined
- Jan 5, 2009
- Messages
- 5,039
on reflection, I now do not see how dropbox could be used as a back end
However, there maybe better alternatives. Amazon host SQL databases in the cloud on something called Amazon Web Services AWS. This is charged for: Active SQL back end databases are charged for based on size, and uptime. Other than a complicated connection string they work as if they were local, and therefore are suitable for this sort of exercise.
They give you a free account for a month, to test it out.
I have a very poor broadband at home, and abandoned it, as I was not getting acceptable speed, but it is worth a try. It worked for me, but just slowly. A fast fibre connection might be OK. If this doesn't give you an acceptable speed, I can't see that dropbox (even if it was technically able to do it) would be any different.
I am sure other providers such as Rackspace might offer similar faciliites to Amazon.
Hope this helps
----
final thought. I think something like this ought to be an easier solution than trying to actually recode a database for web use. Far easier
Dave
I believe we are in basic agreement. There are many solutions including the writing of a Web based program. But if you are looking for a simple cost effective solution then Dropbox is not it.
The best I have come up with is to place the Backend into Dropbox which is installed on the server.
A copy is updated on each users Dropbox whenever the server copy changes. This is fine for all users who have access to the server.
Those who do not are given Read Only privlidges. When required they update their Dropbox via any internet connection. They can then view the latest data but cannot update/edit etc.
The Front End must be programed to tell the difference between a connection to the server as opposed to the copy on their own PC.
I need to do some live testing to see if the results are what I expect.