Access 2013:分发FE或将共享的网络驱动器留在拆分的DB上 [英] Access 2013: Distribute FE or leave on shared network drive for split DB

问题描述

只是想知道对拆分数据库的前端部分最好的做法是什么.该公司拥有每个人都可以访问的共享驱动器，并且后端实际上是该驱动器所在的位置.只是想知道是否最好将FE的副本分发给每个人，或者我是否应该将它们指向共享驱动器上FE的方向.尽管我知道有软件可以帮助管理有限元分配，但后者似乎更易于维护.

Just wondering what the best practice is for the front-end portion of a split database. The company has a shared drive that everyone has access to and is where the back-end actually is. Just wondering if it is better practice to distribute a copy of the FE to everyone or if I should just point them in the direction of the FE on the shared drive. The latter seems easier to maintain although I know there is software to help manage FE distribution.

推荐答案

那么[将前端的单独副本分发给每个用户]仍然是最佳实践吗?

so is it that [distributing a separate copy of the front-end to each user] even still best practice?

是的，即使在2016年，这也不只是最佳实践，绝对可靠对于多个并发用户的可靠操作也是必需的.

Yes, even in 2016 it is not only the best practice, it is absolutely required for reliable operation with multiple concurrent users.

让每个人都访问共享服务器上的单个FE文件有什么好处?

What would the benefit be over having everyone access a single FE file on a shared server?

当多个并发用户打开前端数据库文件的同一副本时，Access将对打开对象(主要是窗体及其关联的记录集)的状态感到困惑.来自后端的数据可能会显示，但实际上在表级别可能没有被破坏.

When multiple concurrent users open the same copy of a front-end database file Access will get confused about the state of open objects (primarily Forms and their associated Recordsets). The data from the back-end can appear to be corrupted, although it may not actually be corrupted at the table level.

当多个并发用户各自拥有自己的前端文件本地副本时，Access不会引起混淆，并且应用程序可以正常工作.那是好处.

When multiple concurrent users each have their own local copy of the front-end file Access does not get confused and the application works correctly. That is the benefit.

这篇关于Access 2013:分发FE或将共享的网络驱动器留在拆分的DB上的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！