是否可以使用 MySQL 表创建 Access 运行时以分发给其他人？
我对分发数据库相当陌生，并且不确定这是否可以在不必包含 MySQL 驱动程序或其他内容的情况下实现。
I am rather new at distributing databases and am unsure if this is possible without having to include MySQL drivers or whatever.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我不得不说这是我听过的最奇怪的组合之一。
Windows 不包括 MySQL 连接。因此，您必须随应用程序一起提供并安装 MySQL 驱动程序。
I have to say it's one of the oddest combinations I've heard of.
Windows does not include MySQL connectivity. Therefore you would have to ship and install MySQL drivers with your application.
我不确定你的问题是什么，因为你的措辞方式让人觉得你理解这些问题。
是的，您可以创建不包含 MySQL 支持的 Access 运行时安装（假设已安装）。
我没有使用最近的运行时分发工具，但旧的工具用于允许您链接安装程序，或包含来自运行时外部的组件进行安装。但是，我当时没有使用 ODBC，所以不知道问题是什么。
您可以使用 Inno 安装程序之类的工具来安装运行时和 MyODBC 驱动程序的单个软件包。
如果您尝试过其中任何一个并遇到问题，也许您应该编辑您的问题以纳入该信息，因为这将帮助人们提供更好的答案。
I'm not sure what the question is, as the way you've worded it makes it seem like you understand the issues.
yes, you could create an Access runtime install that doesn't include the MySQL support, on the assumption that it's already installed.
I haven't used the recent runtime distribution tools, but the old ones used to allow you to chain installers, or include components from outside the runtime for installation. However, I didn't use ODBC back then, so don't know what the issues are for that.
you could use something like the Inno installer to have a single package that installs your runtime and your MyODBC drivers.
If you've tried any of these and run into problems, perhaps you should edit your question to incorporate that information, since that will help people provide better answers.
在我之前的工作场所，有一个使用 MS Access VBA 和 MySQL 的旧应用程序。我们过去使用 MySQL ODBC Connector 来分发它，并将配置存储在本地 MS Access 表中。
起初，该应用程序依赖 DSN ODBC 来存储登录信息，但后来我们转向了我上面提到的内容。
我试图说服我的老板将应用程序转移到 .NET Framework，但我没有成功，因为他喜欢 VBA。
In my previous workplace there were an old application using MS Access VBA and MySQL. We used to distribute it with MySQL ODBC Connector, and storing the configuration in a local MS Access table.
At first the app relies on DSN ODBC to store the login information, but then we moved to what i mentioned above.
I tried to convince my boss to move the app to the .NET Framework but i didn't succeed because he loves VBA.