将一个Access前端拆分为库 [英] split one Access front-end into libraries

问题描述

我有一个非常大的前端访问应用程序和一个SQL Server后端。

I have a very large front-end access application with a SQL Server back-end.

用户定期遇到内存问题，可能是因为超过了VBA模块的数量。

The users are running into memory problems on a regular basis and it might be because of exceeding the number of VBA modules.

我正在考虑将我当前的MDE分成多个代码库，以便根据需要使用。

I'm considering splitting my current MDE into multiple libraries of code to use as needed.

这是解决我问题的可行方案吗？如果是这样，有关最佳实践的指南吗？

Would this be a viable solution to my problem? If so, any guide on best practices to accomplish that?

我的目标是：

• 减少内存占用我的应用程序
• 更快地加载和处理最常见的代码
• 易于管理的代码

我的目标不是创建可重用的库，但要以这样的方式拆分它，使得在应用程序启动时不会自动加载最少使用的代码。

My goal is not to create reusable libraries but to split it in such a way that the code that's the least used is not loaded automatically when the application starts.

谢谢！

推荐答案

模块的数量应该不是问题。那么，您有多少以及如何分发（表单，报告，标准模块和类模块）。内存占用量与内存中的数据量相关（活动查询，实例化
类）。您想要的性能（更快加载和处理最常见的代码）就像它一样，特别是当您已经使用预编译代码时。易于管理：考虑将您的应用程序拆分为模块..

The number of modules should not be a problem. Well, how many do you have and how are the distributed (forms, reports, standard modules and class modules). The memory footprint is correlates more with the amount of data in memory (active queries, instantiated classes). Performance like you want (faster loading and processing of the most common code) is as it is, especially as you already used precompiled code. Easy to manage: Consider splitting your application into modules..

这篇关于将一个Access前端拆分为库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！