如何将更新分发到Access数据库前端? [英] How do I distribute updates to a Access database front end?

问题描述

我已经开发了一个Access 2007数据库，该数据库连接到SQL Server进行实际的数据存储.我使用打包解决方案向导"创建了一个可分发的安装程序，其中包括访问运行时(带有ACCDE文件)，该运行时我已安装并安装在15台左右的PC上.无论如何，我的问题是，将更新分发到该数据库的最佳方法是什么?现在，我需要四处走走，然后重新安装.没问题...我只是想知道是否还有另一种方法.

I've got an Access 2007 database that I developed which connects to SQL Server for the actual data storage. I used the Package Solution Wizard to create a distributable installer which included access runtime (with an ACCDE file) which I went around and installed on 15 or so PCs. Anyway, my question is, what is the best way to distribute updates to this database? Right now I'd need to go around and remove and reinstall. That's not a problem... I was just wondering if there was another way.

我尝试将前端留在网络共享上，但似乎大多数人建议将前端存储在本地计算机上，这是有道理的.当我将其保留在网络共享上时(至少与Access 2003 mdbs共享)，我遇到的问题是我发现自己需要经常压缩和修复，而且我还必须终止打开的会话(已打开文件的用户) )时进行升级.我可以想象，如果用户不在本地网络上，它也可能会造成不必要的瓶颈.

I've tried leaving the front end on a network share but it seems that most people suggest storing the front-end on the local machine, which makes sense. The problems I've run into when I leave it on a network share (at least with Access 2003 mdbs) is that I find myself needing to compact and repair often and I also have to kill the open sessions (user's who have the file open) when upgrading. I would imagine it could also hypothetically create an unnecessary bottleneck if the user was not on the local network.

推荐答案

自动化前端分发很简单.这是一个反复解决的问题. Tony Toews的 http://autofeupdater.com 是这样一种解决方案，它非常容易实现，并且对最终用户完全透明.

Automating front-end distribution is trivial. It's a problem that has been solved repeatedly. Tony Toews's http://autofeupdater.com is one such solution that is extremely easy to implement and completely transparent to the end user.

这篇关于如何将更新分发到Access数据库前端?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！