They've also finally dropped the runtime option. You can still get an on premis server, but it's not cheap. It's just not as affordable for small operations as it used to be. So just for two people, that's $456 a year.
They've dropped peer-to-peer sharing from the standalone product, so now your best option is to use their cloud service, which is a monthly $19/user subscription. You seem to be asking whether FileMaker is a viable multiuser database solution. Do any of you Mac users have experience doing something similar limited to to what campitel actually wants, using FileMaker Pro Advanced or FileMaker Pro Server over a LAN or WAN-even though there's no "real SQL backend (with properly-designed databases), and a web interface"? I feel these posters are urging campitel to unnecessarily "go whole hog"-without any reported programming experience other than a bit of Visual Basic back in 2007–2008. Making "production" database applications is serious business. Anything else is a half-measure that will bite you in the ass.Įither learn how to do this stuff, hire somebody to do it for you, or find some kind of free and/or open-source solution that already does what you want. You *want* a real SQL backend (with properly-designed databases), and a web interface.
But the fact is, if you want to create a *real* database application, there aren't any shortcuts. The first reaction to my post was from Frennzy:īased on 17 years of personal use, I'd suggest Claris FileMaker.įilemaker is better than Access, probably. (I'm not copying my 4.5-paragraph post here you can find it on the first page of that thread.) I then pointed out that I've no personal experience with multi-user FileMaker databases, but cited an Australian consultant who has made a business of setting up and monitoring FileMaker Pro Server databases for Windows-using customers at their sites. I summarized my own 16 years experience with a single-user FileMaker Pro database with referential integrity I created for Mac in 2004. I suggested using FileMaker Pro for Windows. I have no idea how to do that and the security implications make my head hurt. Is there a way to make this work? Are there other solutions I should consider? Writing a web front end to a MySQL DB is not an option. I want someone else to be able to use it too, and they are not in the same building with me. Pretty basic stuff, but something a bit more structured than a spreadsheet would provide. It would have a few tables with some links between them enforcing referential integrity. It will likely hold a few thousand, or maybe one day, a few tens of thousands of records. I would like to use Microsoft Access for a small database.
0 kommentar(er)
