Access将如何生存 [英] How will Access Survive
问题描述
Access如何在一年内公平？两年？ ....新版本的
Access似乎为非程序员提供服务，作为向导界面，通过花哨的向导快速创建数据库。此外，为什么当你在SQL Express中有一个很好的
优质选项时，你甚至会继续使用Access作为后端？
作为未来的前端开发工具怎么样？让我们变得严肃起来。
微软继续发布大量文章和视频，说明你如何只用几行代码就可以创建一个可行的数据网格（这么多
为RAD开发工具的参数）。带来XML和.NET中断开的数据集架构的无数优势
我更确信Access将开始消亡（缺少
对遗留系统的支持）。
重点不是开始骚乱，而是寻求有效的论据
访问将来会公平。提前感谢您的意见。
Jason
希望你会得到几个
水晶球凝视的不同观点。
细节在线。
-
Allen Browne - 微软MVP。西澳大利亚州珀斯。
访问用户提示 - http：// allenbrowne.com/tips.html
回复群组，而不是mvps dot org的allenbrowne。
< ja **** *@bigriver.net>在消息中写道
news：11 ********************** @ 38g2000cwa.googlegro ups.com ...Access如何在一年内公平？两年？ ....新版本的
Access似乎为非程序员提供服务，作为向导界面，通过花哨的向导快速创建数据库。
看起来微软似乎正在强调Access作为桌面数据库的作用，并付出了很多努力使其尽可能地可用于
非程序员。但是他们没有从开发者手中夺走任何东西，而且实际上给我们带来了几个有用的东西。
此外，为什么你甚至会继续使用Access作为当你在SQL Express中有一个很好的选择时，后端是什么？
除了复制MDB并在
计算机上运行它之外，没有其他任何事情可做。我主要与小型企业和非盈利组织合作，他们没有IT员工，更不用说DBMA了。没有其他任何东西如此简单和适当
对他们来说。没有其他任何东西可以像集成的那样无缝地工作了。
Access（JET存储。）
作为未来的前端开发工具怎么样？让我们变得严肃起来。
微软继续发布大量文章和视频，说明你如何只用几行代码来创建一个可行的数据网格（这么多的论点是RAD开发工具）。带来XML和.NET中断开连接的数据集体系结构的无数优势
我更确信Access将开始消亡（缺少对遗留系统的支持）。
当一些东西和Access一样好时，MS和其他的b $ b公司会尝试生产其他具有类似功能的产品。这对于其他工具来说非常好，并且它可能使他们能够侵占某些区域
访问权限只有，但它不会从Access中消失。 />
Access的最大限制是厚客户端方法永远不会被设计为在缓慢或不稳定的连接上工作。这仅仅意味着
访问不适合该市场;它不需要Access的'
优势就可以实现它的设计目标。但是，越来越多的人想要在这些类型的连接中使用他们的数据库，因此适用于Access的场景范围正在缩小。
这当然是一种权衡。如果你想一次加载20个表单，每个表单包含10个子表单，每个子表单有多个组合框，每个表单包含数千个
的记录，你将不可能通过缓慢的
连接实现这一目标。所以你要么放弃胖客户端方法（使用
除了Access之外的其他东西），要么放弃慢速连接和
保持Access灵活性，或者你在
两个之间做出妥协。
无论人们在这个平衡问题上做出具体选择，
无论微软想要支持它（台式机数据库）还是超出他们想要的地方（拥有数十个局域网的用户和数百万条记录），访问仍将具有重要的未来。）
另一家公司可能会创建一个更好的桌面数据库
一天。除非发生这种情况，否则Access仍将是最畅销的数据库
。
ja ***** @ bigriver.net 写道：我更确信Access将开始消亡（缺少
支持遗留系统。）
发布到CDMA
2006年1月1日 - 2006年5月23日：15900（来源 - > Google网上论坛）
也许，这表明Access已经开始消亡几年
前。也许它只是意味着找到了其他更好的帮助来源和
讨论。
我不再使用Access进行个人项目了，主要是因为我/>
想要在安装了最少的b / b
软件的机器上随处使用的应用程序。我发现HTA，ASP / ADO和最近的ASP.Net/ ADO.Net
更适合这个。也许其他开发人员和企业类似于
。
三个无关紧要的问题也让我在MS和Access上感到恶心。一个是一般的MS产品攻击漏洞。
二是VBA;
我尝试学习其他语言/脚本/技术的次数越多我就会认为MS必须尽快咬紧牙关并留下不合时宜的美元
落后。三是ADP的讽刺，这个伟大的梦想导致我们失败，似乎现在已经过时了。
如果我年轻的话，我想我试图完全离开MS世界
。
我同意，Lyle。值得一提的另一点是Visual Studio内置的
部署功能，其中应用程序可以通过Web服务器自动检查和下载更新，或者
中央网络位置。当然，SQL快递有问题
，你必须小心覆盖数据，但你可以通过将数据库作为资源附加来为此编写代码比
a项目文件。当然要更新Access前端。
How will Access fair in a year? Two years? .... The new version of
Access seems to service non programmers as a wizard interface to
quickly create databases via a fancy wizard. Furthermore, why would
you even continue to use Access as a backend when you have a much
superior option in SQL express?
What about as a future front-end development tool? Let''s get serious.
Microsoft continues to publish numerous articles and videos on how you
can whip up a workable datagrid with only a few lines of code (so much
for the argument for the RAD development tool). Bring XML and the
countless advantages of the disconnected dataset architecture in .NET
and I am more convinced that Access will start to die out (short of
support for legacy systems).
The point is not to start a riot but rather seek valid arguments on how
Access will fair in the future. Thanks in advance for your input.
Jason
Hopefully you will get several divergent views from this exersise in
crystal-ball gazing.
Specifics in-line.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
<ja*****@bigriver.net> wrote in message
news:11**********************@38g2000cwa.googlegro ups.com...How will Access fair in a year? Two years? .... The new version of
Access seems to service non programmers as a wizard interface to
quickly create databases via a fancy wizard.
It does look as if Microsoft is emphasizing the role of Access as desktop
database, and putting in lots of effort to make it as usable as possible for
non-programmers. But they have taken away nothing from developers, and
actually given us several useful things as well.
Furthermore, why would
you even continue to use Access as a backend when you have a much
superior option in SQL express?
Nothing else is as simple as just copying an MDB and running it on a
computer. I work mostly with small business and not-for-profit groups who
have no IT staff let alone DBMAs. Nothing else is as simple and appropriate
for them. And nothing else works as well and seamlessly as the integrated
Access (JET storage.)
What about as a future front-end development tool? Let''s get serious.
Microsoft continues to publish numerous articles and videos on how you
can whip up a workable datagrid with only a few lines of code (so much
for the argument for the RAD development tool). Bring XML and the
countless advantages of the disconnected dataset architecture in .NET
and I am more convinced that Access will start to die out (short of
support for legacy systems).
When something is as good as Access, it makes sense that MS and other
companies will try to make other products that have similar features. That''s
great for the other tools, and it may enable them to encroach on areas
Access had exclusively, but it does not take away from Access.
The biggest limitation of Access is that the thick-client approach was never
designed to work over a slow or unstable connection. This simply means
Access is unsuitable for that market; it takes nothing away from Access''s
strengths for what it was designed for. However, more and more people do
want to use their database across these kinds of connections, so the range
of scenarios where Access is suitable is narrowing.
This is a trade-off, of course. If you want to load 20 forms at once, each
with 10 subforms that each have multiple combo boxes with thousands of
records in each, you are not going to be able to achieve that over a slow
connection. So you either move away from the thick-client approach (use
something other than Access), or you give up on the slow-connection and
retain the Access flexibility, or you settle on some compromise between the
two.
Regardless of what specific choices people make on that balance question,
Access will still have a significant future both where Microsoft wants to
pitch it (desktop database) and beyond where they want it (LANs with dozens
of users and millions of records.)
It is possible that another company will create a better desktop database
one day. Unless that happens, Access will still be the best-selling database
of all time.
ja*****@bigriver.net wrote:and I am more convinced that Access will start to die out (short of
support for legacy systems).
Posts to CDMA
Jan 1 2000 - May 23 2000: 85400
Jan 1 2006 - May 23 2006: 15900 (source -> Google Groups)
Perhaps, this indicates that Access started to die out several years
ago. Perhaps it simply means that other better sources of help and
discussion were found.
I do not use Access for personal projects anymore, mostly because I
want applications which can be used anywhere, on machines with minimal
software installed. I find HTAs, ASP/ADO and lately ASP.Net/ ADO.Net
better suited for this. Perhaps other developers and businesses are
similar.
Three extraneous issues have soured me on MS and Access as well. One is
the vulnerability of MS products in general to attack. Two is VBA; the
more I try and learn other languages/scripts/technologies the more I
think that MS must bite the bullet soon and leave this anachronism
behind. Three is the travesty that are ADPs, this great dream that led
us on, failed and seem now to be passé.
If I were younger I think I would be trying to leave the MS world
entirely.
I agree, Lyle. Another point worth mentioning is the built-in
deployment features of Visual Studio where the application can
automatically check for and download updates via a web server or a
central network location. Sure, there are issues with SQL express
where you have to be carefully of overwriting the data, but you can
write code for this by attaching the database as a resource rather than
a project file. Sure beats updating Access front-ends.
这篇关于Access将如何生存的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
