使用Microsoft Access作为MySQL数据库的前端？ [英] Using Microsoft Access as a front-end to a MySQL database?

问题描述

我的Microsoft Access数据库（FE / BE）已经成长的限制，我不得不导入更多的数据，所以Access不再是我正确的选择。我将切换到MySQL（NOT SQL Server）作为一个好的替代，但我想知道什么用作MySQL数据库的前端。我应该保留我的访问VBA代码和前端（使用ODBC连接）或...？不需要高性能。

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.

另一方面，如果你不喜欢在Access和应用程序开发，你有相对微不足道，而你有一个最喜欢的开发平台，你可以很容易地启动和运行非常快，事情向另一个方向。

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.

此外，如果你有一个需求的变化，因为需要在网络或远程用户上部署，这可能是放弃在Access前端投资的一个很好的理由。

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.

这篇关于使用Microsoft Access作为MySQL数据库的前端？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！