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

查看:16
本文介绍了如何持续开发和部署 Access 2010 数据库应用程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

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

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

其中讨论了拆分、编译、安装等,但它们对要遵循的实际程序步骤非常短.

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

我已将我的数据库应用程序拆分为后端和前端:Skill_Back.accdbSkill_Front.accdb.后端位于网络共享驱动器上,一些用户拥有前端的副本.到目前为止一切顺利,尤其是如果我永远不必再进行任何开发.但我现在不太明白如何在不干扰实时"后端的情况下继续前端开发.

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.)

附录

为了进一步遵循以下正确答案中的建议,我发现了一些其他确实描述程序的文章:

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

推荐答案

这不是网站,也不是文件;它是一个数据库.您无法在每个用户的计算机上更新前端的每个副本,它只是不能那样工作.

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.

我使用的一个策略是版本化"我的前端,当我处理数据库时,我不使用 Access 的内置 Move Data 工具.

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?

您(至少)需要 2 个不同的环境

You need (at minimum) 2 different environments

  1. 生产(您的用户使用什么)
  2. 测试(您进行更改并对其进行测试)

对于测试,您需要自己的后端和前端.这是您将进行持续发展的地方.您永远不想打扰用户正在处理的内容,尤其是数据.

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.

对于生产,您可以进行更改并通过共享网络驱动器推出新版本,用户可以在其中下载副本,就像第一个一样.您将在此处使用 Linked Table Manager 将表重新连接到生产后端和新前端.

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.

所以工作流程是:

  1. 您有用户正在使用的生产后端和前端.
  2. 您有这两个数据库的副本可供使用,这与它们使用的内容无关.
  3. 您可以通过 Linked Table Manager 将前端表链接到后端的复制开发版本.
  4. 您在您的前端进行更改/进行更新/继续开发.
  5. 您测试它们/确保一切正常
  6. 您将新的生产前端版本 (v2) 放在共享网络驱动器上,并将其连接到生产后端
  7. 您的用户下载(复制)新的前端版本并使用它.
  8. 他们看到了您的变化,并对您所做的事感到惊讶,而且您因为知道该做什么并成为一名出色的开发人员而获得了 5,000.00 美元的加薪.
  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.

这样可以轻松管理链接.在要更改的每个链接表旁边的框中打勾.或者,如果将它们全部更改,请单击全选.还要选中标记为始终提示输入新位置"(位于该对话框窗口的左下角)的框.然后 Access 会要求您定位链接的数据库源.

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.

如果我有一个包含表的后端数据库,并且我想将这些表链接到桌面上的前端,我会遵循以下流程:

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. 单击 Access 功能区顶部的外部数据"选项卡
  2. 点击访问
  3. 为您的后端选择正确的文件名/目录
  4. 选择通过创建链接表链接到数据源.
  5. 选择要导入的表(大概可以点击全选)
  6. 点击确定".

现在您将在前端看到表格.然后,您可以使用链接表管理器来管理这些链接,例如,如果您的后端数据库移动到不同的位置.

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屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆