Where can I find an overview (website) of best practices for implementing an Microsoft Access application (with a FE/BE architecture) regarding to security, performance and maintainability? I know about designing tables, queries, forms and so on and I'm a reasonable programmer, but I'm wondering what's the "best" and most efficient way to implement my Access application.
我在哪里可以找到实现Microsoft Access应用程序(与FE/BE体系结构)有关安全性、性能和可维护性的最佳实践的概述(网站)?我知道如何设计表、查询、表单等等，我是一个合理的程序员，但我想知道实现我的访问应用程序的“最佳”和最有效的方式是什么。
Thanks in advance for your help.
谢谢你的帮助。
3 个解决方案
#1
5
Take a look at Tony Toews' Best Practices for Microsoft Access. Since you're developing a split application you owe it to yourself to also consider Tony's Auto FE Updater. That utility (which he offers for free) makes it fairly easy to roll out your application front end to the users, and make sure that they are always working from your latest app version.
看看Tony Toews的Microsoft Access最佳实践。既然您正在开发一个分割应用程序，那么您也应该考虑一下Tony的Auto FE更新程序。这个实用程序(他免费提供)使你可以很容易地向用户推出你的应用程序前端，并确保他们总是使用你最新的应用程序版本。
I will also suggest you try to avoid basing your application's forms on large data sets. For example, rather than binding a form directly to a large table, bind it to a query which returns only one or a few rows from the table. Allow your users to select which row or rows they are interested in at any given time. The point here is to limit the amount of data Access must retrieve when the users open your form.
我还建议您尽量避免将应用程序的表单基于大数据集。例如，与其将表单直接绑定到大型表，不如将其绑定到只从表返回一行或几行的查询。允许用户在任何给定的时间选择感兴趣的行或行。这里的要点是限制用户打开表单时必须检索的数据访问数量。
#2
2
Here are a few links to get you started
下面是一些让你开始的链接
http://www.mvps.org/access/
http://www.lebans.com/
http://www.blueclaw-db.com/
Right time to don my flame suit once more and fire up the bound –v- unbound debate once again. Personally I almost always use unbound forms for new work for the control and performance they offer.
现在是时候再一次穿上我的火焰服，再一次点燃装订的无束缚的辩论。就我个人而言，我几乎总是使用未绑定的表单来为他们提供的控件和性能进行新的工作。
The counter argument to that is by using unbound forms you are chucking away a lot of what makes access access however for me anyway I maintain that the greater control and performance outweighs that and once you get into the swing of it I would say the development time is only very slightly longer.
反驳是通过释放形式你外卖的很多访问访问但是总之我认为更大的控制和性能比,一旦你进入它的摇摆我认为开发时间只是略微更长。
#3
2
Interesting topics around Access 2007: http://allenbrowne.com/Access2007.html
有关Access2007的有趣主题:http://allenbrowne.com/Access2007.html
#1
5
Take a look at Tony Toews' Best Practices for Microsoft Access. Since you're developing a split application you owe it to yourself to also consider Tony's Auto FE Updater. That utility (which he offers for free) makes it fairly easy to roll out your application front end to the users, and make sure that they are always working from your latest app version.
看看Tony Toews的Microsoft Access最佳实践。既然您正在开发一个分割应用程序，那么您也应该考虑一下Tony的Auto FE更新程序。这个实用程序(他免费提供)使你可以很容易地向用户推出你的应用程序前端，并确保他们总是使用你最新的应用程序版本。
I will also suggest you try to avoid basing your application's forms on large data sets. For example, rather than binding a form directly to a large table, bind it to a query which returns only one or a few rows from the table. Allow your users to select which row or rows they are interested in at any given time. The point here is to limit the amount of data Access must retrieve when the users open your form.
我还建议您尽量避免将应用程序的表单基于大数据集。例如，与其将表单直接绑定到大型表，不如将其绑定到只从表返回一行或几行的查询。允许用户在任何给定的时间选择感兴趣的行或行。这里的要点是限制用户打开表单时必须检索的数据访问数量。
#2
2
Here are a few links to get you started
下面是一些让你开始的链接
http://www.mvps.org/access/
http://www.lebans.com/
http://www.blueclaw-db.com/
Right time to don my flame suit once more and fire up the bound –v- unbound debate once again. Personally I almost always use unbound forms for new work for the control and performance they offer.
现在是时候再一次穿上我的火焰服，再一次点燃装订的无束缚的辩论。就我个人而言，我几乎总是使用未绑定的表单来为他们提供的控件和性能进行新的工作。
The counter argument to that is by using unbound forms you are chucking away a lot of what makes access access however for me anyway I maintain that the greater control and performance outweighs that and once you get into the swing of it I would say the development time is only very slightly longer.
反驳是通过释放形式你外卖的很多访问访问但是总之我认为更大的控制和性能比,一旦你进入它的摇摆我认为开发时间只是略微更长。
#3
2
Interesting topics around Access 2007: http://allenbrowne.com/Access2007.html
有关Access2007的有趣主题:http://allenbrowne.com/Access2007.html