如何管理“发布"使用 MS Access [英] How to manage "releases" with MS Access

问题描述

我有一个 MS Access 2016 应用程序，有几个人在一个部门使用.我知道整个事情都由网络开发人员编写，但这个访问数据库已经有一段时间了，现在没有时间切换.

I have an MS Access 2016 application that a few people use in one department. I know this whole thing has web dev written all over it but this access database has been their process for a while and there is no time right now to switch over.

最近，一个不同的部门想要使用这个应用程序，但有自己的副本.目前，如果我需要进行更改，我将在应用程序的副本中进行更改，当我准备好导入他们的数据时，他们会向我发送当前版本，我将其导入并将新版本发回给他们.但是，目前我逐表复制数据并将其传递到新数据库中.这是低效和乏味的，现在有 2 组数据我要这样做，这太疯狂了.有超过 20 个表，所以我不想在 2 个应用程序中手动复制 40 多个表，即使是最小的更改，例如更改给用户的消息.

Recently, a different department wants to use this application, but having their own copy. Currently, if I need to make changes, I'll make the changes in a copy of the app, they send me a current version when I'm ready to import their data, I import it and send them back a new one. However, currently I copy the data table by table and past it into the new database. This is inefficient and tedious, and now with 2 sets of data I'd be doing this for, that's crazy. There's over 20 tables so I don't want to have to manually copy over 40+ tables across the 2 apps for even the smallest change like altering a message to the user.

我知道我可以复制代码，这样我就可以避免导入数据，但有时对于大的更改，我会更改 15-20 个 vba 文件.

I know I can copy the code so I can avoid importing the data, but sometimes for big changes I'll change over 15-20 vba files.

所以，有几个问题:

1.有没有办法为我可以在脚本中运行的整个数据库生成插入语句?因此，当我创建新副本时，我只上传 1 个文件并填充所有数据?

1.Is there a way to generate insert statements for the entire database that I could run in a script? So when I create the new copy I just upload 1 file and it populates all the data?

2.是否有任何类型的开发工具可以帮助这个过程?现在我认为这只是创建 MS Access 应用程序的失败，但必须有某种方式人们使新发布"过程变得更容易.我当前的系统似乎有缺陷，我希望有一个更稳定的过程.

2.Are there any kind of dev tools that will help this process? Right now I'm thinking that it's just a downfall of creating an MS Access app, but there must be some way that people have made the "new release" process easier. My current system seems flawed and I'm looking to have a more stable process.

目前，我将所有数据都存储在本地，并附加到与前端相同的访问文件中.由于我将有 2 个不同的部门使用相同的功能，我该如何管理数据/前端?这 2 个部门应该有自己的访问文件来使用表单输入数据，因此在 2 个部门之间使用 1 个前端是行不通的.

Currently I have all my data stored locally, attached to the same access file as the front end. Since I will have 2 different departments using the same functionality, how do I manage the data/the front-end? These 2 departments should have their own access file to enter data using the forms, so having 1 front end between the 2 departments won't work.

另外，我应该创建 2 个独立的后端吗?目前，我无法区分从一个部门插入/更改/删除的内容与另一个部门.如果我要附加一个字段，指定谁输入了记录，这将需要我所有查询的完整整体，因为我需要满足最后期限，所以我没有时间进行查询.

Also, should I create 2 separate back-ends? Currently I would have nothing to distinguish what is being inserted/changed/deleted from one department from the other. If I were to attach a field specifying who entered the record, that would require a complete overall of all my queries which I don't have the time for as there are deadlines I need to meet.

推荐答案

首先要拆分数据库.这有一个向导.

First thing is to split the database. There is a wizard for this.

然后你可以在不接触真实数据的情况下维护前端.

Then you can maintain the frontend without touching the real data.

接下来，考虑使用脚本来分发前端的修订版本.我曾经写过一篇关于一种经过验证的方法来处理这个问题的文章:

Next, consider using a script to distribute revised versions of the frontend. I once wrote an article on one proven method to handle this:

在 Citrix 环境中部署和更新 Microsoft Access 应用程序

这篇关于如何管理“发布"使用 MS Access的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！