Access 2016中的变更控制以及开发/原型设计与QA与生产环境的对比 [英] Change Control within Access 2016 as well as Development/prototyping vs QA vs Production environments
问题描述
没有详细说明，只需说我在大规模和多平台/环境中拥有30多年丰富的IT和业务经验，其中单独的开发/原型设计，QA和生产环境是不可协商的以及
作为严格的变更控制。
我最近参与了一个社区项目，使用Access 2016和VBA开发应用程序是一个合理的选择。我最后一次使用Access和VBA是在90年代早期，因此在过去3
个月里有很多学习和教训。在这个时间点，我有一个完整的第三范式关系数据库，它创建了所有必要的参照完整性和关系以及所有核心功能，我仍然有一些"铃声和口哨"。去完成。 I
我现在可以或者想要实现该应用程序。
我很快意识到变更控制可能是一个"问题"。与我熟悉的环境相比，例如移动已更改的数据结构，有或没有数据，代码更改等。
我很感激任何有关如何处理此问题的建议或建议，因为这是一门学科我会喜欢维护。
如果您正在寻找源代码控制，您可能希望看到以下链接的选项：
Without going in to much detail, suffice to say that I have 30+ years extensive IT and business experience in large scale and multi-platform/environments where separate development/prototyping, QA and production environments are non-negotiable as well as strict change control.
I recently got involved in a community project and was it a logical choice to develop an application using Access 2016 and VBA. The last time I used Access and VBA was during the early '90's, thus there were a lot of learnings and lessons over the past 3 months. At this point in time I have a fully 3rd normal form relational database created with all the necessary referential integrity and relationships and all the core functionality in place, I still have some "bells-and-whistles" to complete. I am at a point now where I can or want to implement the application.
I soon realised that change control may be an "issue" compared to the environments I am familiar with, e.g. moving changed data structures with or without data, codes changes etc.
I'd appreciate any advice or suggestions as how to deal with this as it is a discipline I'd like to maintain.
If you are looking for source code control, you may want to see the below link for options:
http://www.codekabinett.com/rdumps.php?Lang=2&targetDoc=choose-source-code-control-microsoft-access
这篇关于Access 2016中的变更控制以及开发/原型设计与QA与生产环境的对比的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
