My Microsoft Access database (FE/BE) has grown out of the limitations and I've to import more data, so Access is not the right choice for me anymore. I'll switch to MySQL (NOT SQL Server) as a good alternative, but I'm wondering what to use as a front-end to the MySQL database. Should I keep my Access VBA code and front-end (using a ODBC connection) or ...? High performance is not required.
解决方案
If you've already invested a lot in your front end development, to me it's a no-brainer to keep the Access front end.
On the other hand, if you're not comfortable with developing in Access and the app you have is relatively trivial, and you have a favorite development platform that you can easily get up and running with very quickly, things tip in the other direction.
Also, if you have a change of requirements, such as needing to deploy on the web or to remote users, that can be a good reason to abandon your investment in the Access front end.
But in general, the first choice is to stick with what is already working, and then move on only if there are unresolvable problems with that.
321
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
