如何不断开发和部署Access 2010数据库应用程序 [英] How to Continuously Develop and Deploy an Access 2010 Database Application

问题描述

我一直在开发Access 2010数据库应用程序，让我们称之为 Skill.accdb 。
我正处于要开始部署的阶段，以便用户可以开始使用它，并在同一时间继续开发。
我一直在阅读

• MSAccess-Deployment-Best-Practices ，


• 部署-Access-2007-应用程序和


• 分享方式访问数据库

其中讨论了拆分，编译，安装等，但实际的程序步骤很简单。

我已经拆分了我的数据库应用程序进入后端和前端： Skill_Back.accdb 和 Skill_Front.accdb 。
后端在网络共享驱动器上，一些用户具有前端的副本。
到目前为止这么好，特别是如果我从来没有做任何更多的发展。
但是我看不出现在如何继续开发前端，而不打扰现场后端。

我如何前端的开发版本指向后端的虚拟版本，这样我不会搞砸现场版本？
然后，当我想发布新版本的前端时，我该如何让它再次指向后端的实时版本？

如果我重新拆分（即再次使用Move Data | Access数据库工具）指向一个尚未存在的虚拟后端，我被告知所有的表现在都是空的 - 不是什么我想要。
如果我重新分解以指向实时后端的副本，我被问到是否要替换它 - 也不是我想要的。
如果我这样做，我再次被告知该数据库中没有表，后端数据库将为空。但是我看到它（前端）仍然指向现场后端！

我错过了什么关键概念/工具/程序？
（我不是要求编译或运行时或构建一个安装程序 - 那些是以后的问题。）

附录 / p>

在下面的正确答案中，继续遵循这些建议，我发现了一些其他文章，描述程序：

• MS Access Split数据库架构支持多用户环境，提高绩效和简化维护性


• 将Access数据库拆分为应用程序和数据

解决方案

这不是网站或文件;它是一个数据库。您不能更新每个用户计算机上的前端的每个副本，它不会以这种方式工作。

我使用的策略是版本我的前端，当我处理数据库时，我不使用Access'内置的移动数据工具。

< blockquote>

如何使前端的开发版本指向一个
的虚拟版本的后端，以便我不会搞砸生活
版本？

您需要（至少）2种不同的环境

1. 生产（您的用户使用的）


2. 测试（在哪里进行更改并进行测试）

对于测试，您需要您的自己的后端和前端。这是您将继续发展的地方。您不会想打扰用户的工作，特别是数据。

对于生产，您可以通过共享网络驱动器进行更改并推出新版本用户可以下载副本，很像第一个。这是您将使用链接表管理器将表重新连接到生产后端和新的前端。

所以工作流程将是：

1. 您有一个生产后端和用户正在使用的前端。 / li>
   
2. 您有一份这两个数据库的副本，它们与他们正在使用的内容无关。


3. 您链接前端表通过链接表管理器


4. 您更改/制作后端的复制开发版本更新/继续开发您的前端。


5. 您测试他们/确保一切正常


6. 您将新的共享网络驱动器上的生产前端版本（ v2 ），并将其连接到生产后端


7. 您的用户下载（复制）新的前端版本使用它。


8. 他们看到你的变化，并且惊讶于你做了什么，你得到$ 5,00

链接表管理器

在导航窗格中，右键单击其中一个链接表以打开快捷菜单。从那里，选择链接表管理器。

这样可以轻松管理链接。在要更改的每个链接表旁边的框中放置一个复选标记。或者如果全部更改，请单击选择全部。另外选中标记为始终提示新位置的框（在该对话窗口的左下角）。然后Access将要求您找到链接的数据库源。

如果您需要更多信息，只需说出一些东西。

将新表从后端链接到前端

如果我有一个表的后端数据库，我想将这些表链接到前端我的桌面，我会按照这个过程：

1. 点击访问功能区顶部的外部数据标签


2. 单击访问


3. 为后端选择正确的文件名/目录


4. 选择链接通过创建链接表来获取数据源。


5. 选择要导入的表（可能可以单击全选）


6. 单击确定。

现在，您将看到前端的表。然后，您可以使用链接表管理器来管理这些链接，例如，将后端数据库移动到其他位置。

I've been developing an Access 2010 Database Application, let's call it Skill.accdb. I'm at the stage where I want to start deploying it so users can start using it and continue developing at the same time. I've been reading

• MSAccess-Deployment-Best-Practices,
• Deploy-an-Access-2007-application, and
• Ways-to-share-an-Access-database

which talk about splitting, compiling, installing, etc., but they're very short on actual procedural steps to follow.

I have split my database application into a back-end and a front-end: Skill_Back.accdb and Skill_Front.accdb. The back-end is on a network shared drive and some users have copies of the front-end. So far so good, especially if I never have to do any more development. But I can't quite see how to now continue development on the front-end without disturbing the "live" back-end.

How do I have a development version of the front-end pointing to a dummy version of the back-end so that I don't mess up the live version? And then, when I wish to release a new version of the front-end, how do I get it to point again to the live version of the back-end?

If I re-split (ie, use the Move Data | Access Database tool again) to point to a not-yet-existing dummy back-end, I'm told all the tables are now empty -- not what I want. If I re-split to point to a copy of the live back-end, I'm asked if I want to replace it -- also not what I want. If I do, again I'm told "There are no tables in this database. The back-end database will be empty." and yet I see that it (the front-end) is still pointing to the live back-end!

What critical concept/tool/procedure am I missing? (I'm not asking about compiling or runtime or building an installer -- those are later problems.)

addendum

Further to following the advice in the fine answer below, I found a couple of other articles that do describe procedures:

• MS Access Split Database Architecture to Support Multiuser Environments, Improve Performance, and Simplify Maintainability
• Splitting your Access database into application and data

解决方案

This isn't a website, or a file; it's a database. You can't update every copy of your front end on each user's computer, it just doesn't work that way.

A strategy I use is to "version" my front-ends, and when I deal with databases I don't uses Access' built-in Move Data tool.

How do I have a development version of the front-end pointing to a dummy version of the back-end so that I don't mess up the live version?

You need (at minimum) 2 different environments

1. Production (what your users use)
2. Testing (where you make your changes and test them)

For Testing, you need your own back-end and front-end. This is where you will do your continuous development. You never want to disturb what your users are working with, especially the data.

For production, you can make your changes and roll out the new version via shared network drive where the users can download the copy, much like the first one. This is where you'll use the Linked Table Manager to reconnect the tables to your production back-end and your new front-end.

So the work flow would be:

1. You have a production back end and front end the users are using.
2. You have a copy of both of those databases to work with, and it's not related to what they are using.
3. You link your Front End tables to your copied development version of the back-end via Linked Table Manager.
4. You change/make updates/continue to develop on your front end.
5. You test them/ensure everything works
6. You place your new production front end version (v2) on the shared network drive and connect it to the production back end
7. Your users download (copy) the new front end version and use it.
8. They see your changes and are amazed by what you did and you get a $5,000.00 raise for knowing what to do and being a great developer.

Linked Table Manager

In the Navigation Pane, right-click one of the linked tables to open the shortcut menu. From there, choose Linked Table Manager.

That makes it easy to manage the links. Put a checkmark in the box next to each linked table you want to change. Or if changing them all, click Select ALL. Also check the box labeled "Always prompt for new location" (at the lower left corner of that dialog window). Then Access will ask you to locate the database source for the links.

If you need more info just say something.

Linking New Tables from Back End to Front End

If I have a back-end database with tables and I wanted to link those tables to a front-end on my desktop, I would follow this process:

1. Click on the External Data tab at the top of the Access ribbon
2. Click on Access
3. Select the correct File name/directory for your back-end
4. Select Link to the data source by creating a linked table.
5. Select the tables you want to import (probably can click Select All)
6. Click "OK".

Now you will see the tables in your front end. You can then use the Linked Table Manager to manage these links should, for example, your back end database be moved to a different location.

这篇关于如何不断开发和部署Access 2010数据库应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！