Then you would distribute your front end to your users. You don't need Access or any other db system installed on the server to be able to use it to simply serve the file. Again, using a non-Access db will add slowness and complexity unnecessarily to your system, even if the db performs better than Access internally.īasically, if you have access to a server, then you would just stick your back end (data) file on the server and run it from there. (Basically all databases should be split databases, even if for a single user.) And while I agree with him that putting it on a server would be better than running it off your PC, I disagree that using MariaDB on a server would be a superior solution. I agree with u/KelemvorSparkyfox 's comment that it should be a split database. Plus you'll get better performance, not having to go through ODBC. It's all you need for this, and it will make development much, much faster and easier. It's not needed for what you're describing, and would unnecessarily add a level of complexity to your project. First, no, I would advise against using SQL Server or a different back end for your project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |