On 2015/11/13 9:55 PM, A. Mannini wrote: > Ok, thanks for all your replies!!! > > First, i was asking to understand...before to start development in a > wrong direction. > > I don't have experience with SQLite and even less on a network share. I > would understand if corruption is a remote possibility or a certainty. > > Someone said that Access suffer the same problem... In my experience > even with 20-30 clients with low concurrency (management software) MS > Access file corruption is a rare event. > (the article you linked refer to a bug with an hotfix) > I can't use Access in my case because my application is x64. > > About VistaDB it support use on network share look at > http://www.gibraltarsoftware.com/Support/VistaDB/Documentation/WebFrame.html#VistaDB_Introduction_SupportedPlatforms.html > and confirmed from its support. Unfortunately i have not experiences > with it....i can't say how much this is true... > > Other suggests are welcomed?
Basically the decision is easy - If you require either of: - Network data - User control Then you should use a suited Network DB and not a file-based DB. Best free (without limitations) choices are (In no particular order): - PostGres | http://www.postgresql.org/ - MariaDB / MySQL | https://www.mysql.com/ ... in fact, let me simply link you to a site with a listing already: http://tech.gaeatimes.com/index.php/archive/top-7-free-open-source-database-server/ Personally I just use the two above, MySQL especially for Web things, and PG for Networked systems (but that's just my preference, they both work either way). I use SQLite to store local data always. I don't wish to start a fanboy fight, but my feeling is that: MySQL is easier to code the broad-spectrum SQL for... Postgres is more stable, strict and secure. (My biased views). HTH, Ryan
