拆分MS Access数据库-前端部件位置 [英] Splitting MS Access Database - Front End Part Location

问题描述

最佳实践之一 对于Access Development，Access应用程序分为两部分；前端用于保存除表以外的所有对象，后端则用于保存表.

One of the best practices as specified by Microsoft for Access Development is splitting Access application into 2 parts; Front End that hold all the object except tables and the Back End that holds the tables.

msdn页面链接到文章拆分Microsoft Access数据库以提高性能和简化操作可维护性，详细描述了该过程.

The msdn page links there to the article Splitting Microsoft Access Databases to Improve Performance and Simplify Maintainability that describes the process in details.

建议在多用户环境中，将后端存储在服务器/共享文件夹中，同时将前端分发给每个用户.

It is recommended that in multi user environment the Back End is stored on the server/shared folder while the Front End is distributed to each user.

这意味着每次对前端进行任何更改时，都需要将其部署到每台用户计算机上.

That implies that each time there are any changes made to the front end they need to be deployed to every user machine.

我的问题是:

假设用户本身无权修改应用程序的前端部分，那么将其保留在服务器上以及后端副本旁边的弊端/危险是什么?

Assuming that the users themselves do not have rights to modify the Front End part of the application what would be the drawbacks/dangers of leaving this on the server as well next to the Back End copy?

我可以在此处看到性能问题，但是这里是否存在任何危险，例如可能的损坏等?

I can see the performance issues here, but are there any dangers here like possible corruptions etc?

谢谢

编辑

为澄清起见，有问题的方案假定一个前端存储在服务器上并由用户共享.

Just to clarify, the scenario specified in question assumes one Front End stored on the server and shared by users.

我知道建议将FE部署到每台用户计算机上，但是我的问题更多是如果不这样做会带来什么危险.

I understand that the recommendation is to have FE deployed to each user machine, but my question is more about what are the dangers if that is not done.

例如当您获得使用服务器上同时使用FE和BE的方法的现有解决方案时.假设性能是可以接受的，并且客户不愿更改方法，您是否仍会推动更改?又为什么呢?例如，可能存在数据损坏的危险肯定是足够有力的论据，但事实是这样吗?

E.g. when you are given an existing solution that uses the approach of both FE and BE on the server. Assuming the the performance is acceptable and the customer is reluctant to change the approach would you still push the change? And why exactly? For example the danger of possible data corruption would definitely be the strong enough argument, but is that the case?

这是我之前的问题跟进问题的一部分MS Access 2007

推荐答案

将个人用户专用FE副本保留在服务器上的唯一缺点是网络性能.就数据损坏而言，这不会有任何改变.

The only drawback to leaving the individual user specific copies of the FE on the server is network performance. It won't make a difference as far as data corruption.

但是您不应该在多个用户之间共享FE.这容易导致富裕的腐败和其他怪异现象.每个用户都应获得自己的FE副本.另外，当用户使用它时，您不能将其替换为新副本.

But you shouldn't share a FE between multiple users. This is prone to corruptions on the FE and other weirdness. Each user should get their own copy of the FE. Also you can't replace it with a new copy while users are using it.

一个客户端使用FE在文件服务器上的单个用户文件夹上运行了多年，但在Citrix群集中运行msaccess.exe. IT人员不想对Citrix群集服务器系统的本地硬盘进行任何更新.

A client was running for years with the FE on individual user folders on the file server but running msaccess.exe in a Citrix cluster. The IT staff didn't want to have anything updating the local hard drives of the Citrix cluster server systems.

有关部署FE的信息，请参见我的网站上的 Auto FE Updater .下周将进行巨大的更改，这将使初始服务器安装和用户初始安装变得更加容易.

As far as deploying the FE see the Auto FE Updater at my website. Huge changes coming in the next week to make it much, much easier for both initial server install and easier user initial install.

这篇关于拆分MS Access数据库-前端部件位置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！