vba 实现 Microsoft Access 应用程序的最佳实践

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/2757636/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-09-11 11:36:15  来源:igfitidea点击:

Best practices for implementing an Microsoft Access application

databasevbams-access

提问by waanders

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 架构)的最佳实践概述(网站)?我知道设计表、查询、表单等,而且我是一个合理的程序员,但我想知道实现我的 Access 应用程序的“最佳”和最有效的方法是什么。

Thanks in advance for your help.

在此先感谢您的帮助。

采纳答案by HansUp

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 Updater。该实用程序(他免费提供)使向用户推出您的应用程序前端变得相当容易,并确保他们始终使用您的最新应用程序版本。

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.

我还建议您尽量避免将应用程序的表单基于大型数据集。例如,不是将表单直接绑定到大表,而是将其绑定到仅从表中返回一行或几行的查询。允许您的用户在任何给定时间选择他们感兴趣的一行或多行。这里的重点是限制用户打开表单时 Access 必须检索的数据量。

回答by Kevin Ross

Here are a few links to get you started

这里有一些链接可以帮助您入门

http://www.mvps.org/access/

http://www.mvps.org/access/

http://www.lebans.com/

http://www.lebans.com/

http://www.blueclaw-db.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.

是时候再次穿上我的火焰套装并再次引发有界-v- 无界辩论。就我个人而言,我几乎总是使用未绑定的表单来进行新工作,以获得它们提供的控制和性能。

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.

与此相反的论点是,通过使用未绑定的表单,您将放弃很多使访问权限的东西,但是无论如何,我认为更好的控制和性能胜过它,一旦您开始使用它,我会说开发时间只是稍微长了一点。

回答by user332278

Interesting topics around Access 2007: http://allenbrowne.com/Access2007.html

与 Access 2007 相关的有趣话题:http: //allenbrowne.com/Access2007.html