使用MicrosoftAccess作为MySQL数据库的前端？-UsingMicrosoftAccessasafront-endtoaMySQLdatabase?

1  

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.

此外,如果您需要更改要求(例如需要在Web上部署或远程用户),这可能是放弃对Access前端投资的一个很好的理由。

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.

但总的来说,第一选择是坚持已经有效的方法,然后继续前进,只要有无法解决的问题。

1  

I use access as my front end all the time. It works, plain and simple. You can use the tools in Access to upsize the tables to SQL. After that is done, I rename the linked tables to take out the dbo_ prefix, so the forms and code is all still looking at the same table name.

我一直使用access作为我的前端。它的工作原理简单明了。您可以使用Access中的工具将表升迁到SQL。完成后,我重命名链接表以取出dbo_前缀,因此表单和代码仍然在查看相同的表名。

Now you have sql maintenance and backups of the data. You can make different copies of the front end. You can have a dev copy and one for users. Once you have changes to the front end - new forms or reports, you can publish it in 2 seconds when no one is in the published copy.

现在你有sql维护和数据备份。您可以制作前端的不同副本。您可以拥有一个开发副本和一个用户。一旦您对前端进行了更改 - 新表单或报表,您可以在发布副本中没有人的情况下在2秒内发布它。

I have wanted to learn asp or go to other platforms for front end gui of my db's, but why bother when I don't need a bomb for an ant hill? They are small apps and Access does a good job with them.

我想学习asp或者去我的db的前端gui的其他平台,但是为什么在我不需要炸弹用于蚂蚁山时呢?它们是小型应用程序,Access可以很好地使用它们。

hth!

1  

I think you should at least first try a copy of your existing Access FE with ODBC links to the new MySQL database. I've done similar with PostGreSql and SQL Server as the backend database, and it can work well. I don't know whether you could run into more gotchas or even deal-breakers with MySQL, but seems like it should be worth a try. And it wouldn't cost you much effort to find out ... just discard or rename your existing Jet tables and add the ODBC links in their place.

我认为你至少应该首先尝试使用ODBC链接到新MySQL数据库的现有Access FE的副本。我已经完成了与PostGreSql和SQL Server类似的后端数据库,它可以很好地工作。我不知道你是否会遇到更多陷阱甚至与MySQL打交道,但看起来应该值得一试。并且不需要花费太多精力就可以找到...只需丢弃或重命名现有的Jet表并在其位置添加ODBC链接。