分发访问应用程序 [英] Distributing Access Applications
问题描述
我阅读了Mike Groh在Access-VB-SQL Advisor杂志上发表的一篇文章，
第37周，关于分发Access的问题让我非常关注
应用程序商业上。
首先，我需要描述一个商业版本。我的应用程序
我希望在完成所有beta测试后分发：
A.它是使用MS AccessXP Pro（开发人员版）开发的，
B.它有一个前端MyApplication.mdb和一个MyAppBbackend_be.mde;
前端不是mde这样我就可以提供补丁和
更新。我有代码包括每当提供补丁和更新时自动寻找
后端，
C.我在我的包中包含Access Runtime（和使用，\ runun
开关），以便我的应用程序不会干扰以前的
和最终用户可能已经存在的现有版本的Access
机器（反之亦然，
D.在我的报告表格中，我包括Word和Excel按钮以防万一
人想要将这些程序中的任何一个报告都愚蠢。我没有
有任何访问库引用检查其中任何一个
程序，
E.我将为a-number-of-days到期提供代码，
也会阻止日历回滚，以及扩展的能力
演示/测试日历期;我觉得应该包含的设施
MS Access开发者版中的
。但是，那个'是另一个职位，我客人
F.确定哪些电脑配置我的应用程序可以运行在
。我这样做是为了缩小我的软件要求：
a。操作系统：Windows 98SE，Windows2000 +和XP，含
" MDAC_TYP
版本2.8（减去MS建议的服务器排除（不包括
$ b） $ b？98和？ME）。再过一两年，我可能会删除Win98SE
和2000，因为我继续升级我的开发者版本的Access。
b。计算机：Pentium III最低64毫克，124分钟，推荐，
加上每个Office程序8兆。我正在确定什么配置
我的软件将在测试期间支持，以最大限度地减少对那些许多计算机配置的持续支持。
现在，我读了迈克的这篇文章Groh，部分地说，坏的
新闻是访问应用程序是众所周知难以分发给大量用户的
。事实上，我知道没有商业可用的
用Access编写的应用程序，虽然有一些使用
..MDB文件格式的数据。
他在本文中遇到的一些困难包括:(编辑
空间）
A.存在许多不同版本和格式的Office。
安装Access 2000内置的应用程序可能会，例如，
break已经存在于用户的Access 97应用程序计算机。
Access对注册表设置有重大影响。
B.此外，差异小到拥有不同的Office服务
pack安装足以导致应用程序停止工作或
拒绝正确安装，即安装Access 2000运行时
应用程序导致AOL停止工作。
C.其他Office产品（如Excel，Word或Outlook），这会增加一个或两个复杂程度，因为必要的库可能会不是
那里（或没有正确引用）。
D.在各种计算机配置上安装由于访问应用程序可能非常糟糕，因此存在持续支持的问题。
支持饥饿。
有一次，他状态，你最好的办法是获得一个分配的访问
应用程序投资专业安装
工具，如Wise（ http://www.wise.com ）或InstallShield
（ http://www.installshield.com），然后获取SageKey安装
脚本（< a rel =nofollowhref =http://www.sagekey.comtarget =_ blank> http://www.sagekey.com ）建立您的分发包。
总而言之，您将在安装软件上投入大约1,000美元，并且
必须掌握创建分发包之前才能获得
自信地发送软件进行安装。
最后他建议，&qu ot;如果你还没有看过它，那么VB.Net的开发环境非常酷，并且在大多数现代win操作系统上运行良好。
我的担忧：
1.我在购买MS Office Developer时投入了大量资金
版本以及介于两者之间的所有升级在过去5年中，
已经承担了各种其他开发人员的费用，包括
，（帮助编写程序，自定义代码等等），我是
某些读这篇文章的人都可以欣赏。
现在建议我必须，。 。 。投资大约
还有另外1000美元的安装软件。
" InstallShield"单独的软件花费大约1,200.00美元。
这是真的吗？这笔额外投资的成本是否真的需要建议？
2. VB.Net是否打算取代AccessXP开发者版？愚蠢
提问时间;什么是MS Access开发者版与
VB.Net;他们对彼此有什么影响？
3.当我在我的包裹中包含Access Runtime时（并强制使用
the，" \运行时开关"）开关"）如果我没有在我的Access库中对Outlook，MS Word或Excel等进行任何引用
，那不应该是
解决关于什么是正确引用的问题或什么
被添加到注册表中？
John
I read an article by, by Mike Groh, in Access-VB-SQL Advisor Magazine,
Week 37 that concerns me quite a bit on distributing Access
Applications commercially.
First I need to describe a "commercial version" of my application that
I hope to distribute after completing all the beta testing:
A. It was developed using MS AccessXP Pro (developers edition),
B. It has a front end MyApplication.mdb and a MyAppBbackend_be.mde;
the front end is not an "mde" so that I am able to provide patches and
updates to it. I have code include that automatically seeks out the
back end whenever patches and updates are provided,
C. I include the Access Runtime in my packages (and use the, "\runtime
switch") in order that my application does not interfere with previous
and existing versions of Access that may already exist on end-user
machines (and vise versa,
D. On my report forms I include buttons for Word and Excel in case
people want to dumb reports into either of those programs. I do not
have any Access library references checked for either of those
programs,
E. I will have code for a, "a-number-of-days" expiration that will
also prevent calendar "rollbacks", plus the ability to extend
demo/beta calendar periods; "amenities that I feel should be included
in MS Access Developers Edition. But, that''s another post I guest.
F. Determining what computer configurations my application will run
on; I have so for narrowed my software requirements to:
a. Operating Systems: Windows 98SE, Windows2000+, and XP with
"MDAC_TYP
version 2.8 (minus MS recommended "Server exclusions (does not include
?98 and ?ME). In another year or two, I''ll probably delete Win98SE
and 2000 as I continue to upgrade my developers'' version of Access.
b. Computers: Pentium III with 64mg minimum, 124 min, recommended,
plus 8 meg per Office program. I am determining what configurations
my software will support during testing in order to minimize ongoing
support for the many computer configurations that are out there.
Now, I read this article by Mike Groh, who, in part, states, "The bad
news is Access applications are notoriously difficult to distribute to
large numbers of users. In fact, I know of no commercially available
application written in Access, although there are a few that use the
..MDB file format for their data. "
Some of the difficulties he sites in this article include: (edit for
space)
A. The many different versions and formats of Office that exist.
Installing an application built in Access 2000 might, for instance,
break Access 97 applications already residing on the user''s computer.
Access has a significant impact on registry settings.
B. Also, differences as small as having a different Office service
pack installed are enough to cause an application to stop working or
refuse to install properly i.e., installing an Access 2000 runtime
application causing AOL to stop working.
C. Other Office products (like Excel, Word, or Outlook), this adds a
level or two of complication, as the necessary libraries may not be
there (or not properly referenced).
D. Installing on the various computer configurations there is the
issue of ongoing support as access applications can be notoriously
support hungry.
At one point, he states, "Your best bet in getting an Access
application distributed is to invest in a professional installation
tool such as Wise (http://www.wise.com) or InstallShield
(http://www.installshield.com), then get the SageKey installation
scripts (http://www.sagekey.com) to build your distribution package.
All in all, you''ll invest about US$1,000 in installation software, and
have to master creating distribution packages before you''ll be able to
confidently send out software to install."
Finally he suggests that, "If you haven''t already looked at it the
VB.Net development environment is pretty cool and runs well on most
modern win operating systems."
My Concerns:
1. I have invested lots of bucks in purchasing MS Office Developer
Editions and all the upgrades in between over the past 5 years, and
have incurred all sorts of other developer cost that goes with
it,(help authoring programs, custom codes, etc, etc.), that I am
certain everyone reading this can appreciate.
Now it is being suggested that I''ll have to, ". . . invest about
still another US$1,000 in installation software." The
"InstallShield" software alone cost approximately, $1,200.00 bucks.
Is this for real; is the cost of this additional investment that is
being suggested really necessary?
2. Is VB.Net intended to replace AccessXP Developers Edition? Dumb
question time; what does MS Access Developers Edition have to do with
VB.Net; what impact do they have on each other?
3. When I include the Access Runtime in my packages (and force use
the, "\runtime switch") switch") and if I am not making ANY references
to Outlook, MS Word, or Excel, etc. in my Access library, shouldn''t
that address any issue regarding what is properly referenced or What
gets add to the registry?
John
推荐答案
1,000个安装软件，并且
必须掌握创建分发包之前你能够自信地发送软件安装。
最后他建议，如果你还没有看过它，那么
VB.Net开发环境很漂亮很酷且在大多数现金运行系统中运行良好。
我的担忧：
1.我投资了很多购买中的雄鹿MS Office开发人员
版本以及过去5年间的所有升级，以及
已经产生各种其他开发人员费用
it，（帮助创作程序，自定义代码等等），我是
某些阅读此内容的人都可以欣赏。
现在它正在建议我必须， 。 。投资大约
另一个美国
1,000 in installation software, and
have to master creating distribution packages before you''ll be able to
confidently send out software to install."
Finally he suggests that, "If you haven''t already looked at it the
VB.Net development environment is pretty cool and runs well on most
modern win operating systems."
My Concerns:
1. I have invested lots of bucks in purchasing MS Office Developer
Editions and all the upgrades in between over the past 5 years, and
have incurred all sorts of other developer cost that goes with
it,(help authoring programs, custom codes, etc, etc.), that I am
certain everyone reading this can appreciate.
Now it is being suggested that I''ll have to, ". . . invest about
still another US
1,000个安装软件。
" InstallShield"软件单独花费，
1,000 in installation software." The
"InstallShield" software alone cost approximately,
1,200.00美元。
这是真的吗？这笔额外投资的成本是否真的需要建议？
2. VB.Net是否打算取代AccessXP开发者版？愚蠢
提问时间;什么是MS Access开发者版与
VB.Net;他们对彼此有什么影响？
3.当我在我的包裹中包含Access Runtime时（并强制使用
the，" \运行时开关"）开关"）如果我没有在我的Access库中对Outlook，MS Word或Excel等进行任何引用
，那不应该是
解决有关正确引用的内容或将什么
添加到注册表中的任何问题？
John
1,200.00 bucks.
Is this for real; is the cost of this additional investment that is
being suggested really necessary?
2. Is VB.Net intended to replace AccessXP Developers Edition? Dumb
question time; what does MS Access Developers Edition have to do with
VB.Net; what impact do they have on each other?
3. When I include the Access Runtime in my packages (and force use
the, "\runtime switch") switch") and if I am not making ANY references
to Outlook, MS Word, or Excel, etc. in my Access library, shouldn''t
that address any issue regarding what is properly referenced or What
gets add to the registry?
John
这篇关于分发访问应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
