使用ADP的一个很好的理由 [英] A good reason to use ADP's

问题描述

很久以前，Larry Linson（这个小组的MVP撰稿人）明确表示，mdb'可以做任何事情，ADP'（Access Projects）可以通过使用

链接表以利用SQL Server数据库。从那时起已经好几年了，

，在评估ADP'我构建的

有用性时，我仍然有时会想到这个陈述。拉里和我讨论了这种技术，并且他发现它可信。 （希望你不要介意我引用你的先生）所以

地狱......这就是 - 这是适合所有你顽固的ADP家伙（和gals of
）
课程）。我知道有很多关于手头的b

$ b主题的辩论已经有很长时间了，有些我已经读过并参与过了......也许这个

推荐用法甚至已经浮出水面 - 然而，我觉得它已经没有像拉里回应的那样被提及了。


自从用过ADP之后A2K的诞生，我发现很多适合我的优惠......但是你呢？请理解，这个

线程不是公开邀请来反击ADP'（让我们尝试新的东西），

而是一种建设性的方法来弄清楚人们使用

的伎俩让他们有价值 - 好？所以，没有进一步的延迟......这是一个我的包中的创新技巧，我为自己保留了一些

时间......你的免费如果这对你来说是新的...


请注意，ADP使用OLEDB连接连接到Sql Server。这种类型

的连接可以并且肯定会比本地网络更进一步，实际上它可以跨越到任何有端口1433（Sql Server）打开的IP地址

和Sql Server / MSDE正在运行。也许ADP的最大优势在于我的业务是我可以将它们部署到多个地点，同时在数据库中托管

。按月收费，客户可以获得一个托管数据库，并且不需要支付服务器费用。这个模型只适合小分支

办公场景像手套一样。然后，使用绑定表格和智能

存储过程设计，我有一个非常紧凑，快速的表现（通过保持

记录下来），丰富，信不信由你。 ..安全交付的ADE

申请。


有多少人拥有使用Sql Server数据库的网站？如果是这样的话，你知道你可以用Access作为一个项目来连接它吗？

用数据库做你想做的任何事情...只要你有

凭证？大多数（如果不是所有）主持Sql数据库的ISP允许您与企业管理器连接 - 您可以使用相同的凭据来连接您的Access副本。使用数据，构建新查询，构建一些用于维护数据的表单，将它们部署为构建复杂但基于Web页面的无特殊维护系统的替代方案。 />

我相信这是AccessXP的新功能，但是你知道你现在可以链接

多种风格的表到ADP'了吗？是的，Paradox，dBase，MDB'和任何ODBC

或OLEDB可访问引擎......仅举几例。如果你有一个

的需要，请查看它。你总是可以从Sql Server链接其中的一些，但现在

它是表视图中的右击和链接选项。


无论如何 - 我希望这个主题保持积极态度，揭示ADP为开发人员提供的一些非常好的功能

功能。


专业回复表示赞赏。
< br $> b $ b -

Jerry Boone

Analytical Technologies，Inc。
http://www.antech.biz

ASP，ASP.NET，SQL Server和<的安全托管和开发解决方案br />
访问

解决方案

" Jerry Boone" < JE *** @ antech.biz.killspam>在消息中写道

news：f0 ******************* @ newssvr11.news.prodigy。 com ...

很久以前，Larry Linson（这个小组的MVP贡献者）给了我一个点
，mdb'可以做任何ADP'（访问项目）可以通过使用链接表来利用Sql server数据库。那时已经过了几年多的时间，而且在评估ADP构建的有用性时，我仍然有时会考虑这个陈述。拉里和我讨论了这种技术
，他发现它可信。 （希望你不要介意我引用你的先生）所以，这真是太糟糕了......这就是 - 这是适合所有你辛苦的ADP人（以及当然的女孩）。我知道对手头的主题进行了长时间的辩论，有些我已经阅读并成为了参与者......也许
这个使用建议甚至已经浮出水面 - 但是，拉里回应的方式让我觉得以前没有提到过。

自从A2K诞生以来，在使用ADP之后，我发现了许多适合的优势我......但你怎么样？请理解，这个
主题并不是一个公开邀请来反击ADP'（让我们尝试新的东西），而是一种建设性的方式来弄清楚人们正在使用什么技巧
使他们有价值 - 好？所以，没有进一步的延迟......这是我的包中的一个创新技巧，我为自己保留了一些时间......如果它对你来说是新的，你可以免费获得。 ..

请注意，ADP使用OLEDB连接连接到Sql Server。这种
类型的连接可以并且肯定会超过本地
网络，实际上它可以跨越任何具有端口1433（Sql Server）
打开的IP地址和Sql Server / MSDE运行。也许ADP在我的业务中拥有
的最大优势在于我可以在托管数据库的同时将它们部署到多个位置。对于每月费用，客户获得一个托管数据库，并且不会产生服务器费用。该模型简单地适合小的
分支机构场景像手套。然后，使用绑定表格和智能存储过程设计，我有一个非常紧凑，快速的表现（保持记录下来），丰富，信不信由你...安全交付ADE
有多少人拥有使用Sql Server数据库的网站？如果是这样的话，
你知道你可以用Access作为一个项目
来连接它吗？你可以用数据库做任何你想做的事情......只要你有
证书吗？大多数（如果不是所有托管Sql数据库的ISP）允许您与企业管理器连接 - 您可以使用这些相同的凭据来连接您的Access副本。使用数据，构建新查询，构建
用于维护数据的一些表单，将它们部署为构建基于Web页面的复杂但无特征的维护系统的替代方案。

我相信这是AccessXP的新功能，但您知道现在可以将
链接到ADP的各种表格吗？是的，Paradox，dBase，MDB'以及任何
ODBC或OLEDB可访问引擎......仅举几例。如果你有这个需要，请考虑一下。你总是可以从Sql Server链接其中的一些，但现在它是表格视图中的右键单击和链接选项。

无论如何 - 我希望这个帖子保持积极的态度并揭露一些真的良好的
ADP为开发人员提供的功能。

专业回复表示赞赏。

两点：


我的意图不是打击ADP。而且我不怀疑

ADP的许多功能可以更容易地通过互联网连接到服务器，但是你似乎只要说ADP有这个能力。您正在描述的关于通过互联网连接服务器的所有内容也可以使用ODBC

和MDB文件来完成。


一个不仅限于对链表的Jet查询，因为它们是使用ODBC / MDB文件的
。我有几年使用的应用程序通过互联网连接到我们的SQL Server，并发现即使使用

拨号连接，它也非常实用。这是一个应用程序，它为小数据交易提供了自己的b $ b，几乎所有这些都是使用

存储过程和传递完成的。


第二点关注为什么我必须完全重新设计相同的应用程序

a几年前摆脱ODBC并切换到使用HTTP

请求说话到Java servlets。原因是我被告知我的网络管理员

将端口1433打开到互联网是一个巨大的

安全问题。这个意见几乎得到了一致同意，当我向b $ b做了一些新闻组的询问。如果事实确实如此，那么我想知道，如果定义的内容缺乏适当的安全性，那么你所描述的内容有什么好处。


我同意新版本中链接到除了
SQL Server以外的来源的能力是一个很大的优势。当我第一次在A2000中看到它们时，这是我对它们感兴趣的主要原因。
-

我不喜欢检查此邮件附带的电子邮件帐户

。发送给... ...

在Hunter dot com的RBrandt

谢谢Rick - 非常专业。我对你尊重点的回答是

这些...


用ADP连接和部署......

文件连接 - 填写参数

此时所有Sql对象都是IDE的本地对象，用于设计更改，

将反映对数据库进行的设计更改，而不更新ADE 。

可以随时更改数据库名称以使用连接参数连接到不同的数据库

。例如，相同的会计系统

有4个不同的公司，数据库结构相同，用户可以通过更改这一个选项来选择哪个公司，ADP将坚持

全面的一切。


使用Jet连接和部署...

设计ini或reg条目以在ODBC中创建dsn参数

开始链接表

此时链接表在那里，但表必须重新链接并且

可能重新部署mdb （远程位置和选项有限）

如果对表格进行了更新。数据库名称需要修复，或者

否则必须安装更多的代码和工作。


我的意图是在本地做什么，但代码和访问权限对象。另外......

本地存储，我使用本地xml和atdg文件在应用程序启动时更新一次

为此 - 效果很好。


安全 - *许多行业权威人士（和我）认为Jet安全性是一个矛盾的。似乎有几十种破解Jet数据库的方法

安全性 - 甚至有一些网站只需支付少量费用即可。

如果你''再关注安全问题，切换到MSDE或SQL Server，你将面临另一整套安全问题，但是在哪里它b / b
更容易维护数据库的整体安全性。他提到的

问题涉及到大量的选择。通过

他写的内容，我会说使用Jet会减少SQL Server的安全性。


Sql Server端口1433已经发生了一起安全事件。我的

系统从未受到它的影响有两个原因 - 我只允许1433到

客户端使用静态ip'（信誉良好的商家）并将它们输入我的

防火墙。在更安全的系统上，我移动端口以及使用

防火墙细节。安全不适合新手 - 这是一种随着技术发生变化的进化现象。昨天什么是不安全的，今天是安全的或者至少更安全的。这些问题应定期评估

，而不仅仅是一次。


在7.0版的Sql Server中，数据库的链接是可能的。

*来自William Vaughn关于ADO最佳实践的最新着作 - 第41页，最后

段。


-

Jerry Boone

Analytical Technologies，Inc。
http：/ /www.antech.biz

ASP，ASP.NET，SQL Server的安全托管和开发解决方案和

访问

Rick Brandt < RI ********* @ hotmail.com>在消息中写道

news：bt ************ @ ID-98015.news.uni-berlin.de ...

" ;杰里布恩 < JE *** @ antech.biz.killspam>在消息中写道
新闻：f0 ******************* @ newssvr11.news.prodigy。 com ...

很久以前Larry Linson（这个组的MVP贡献者）将$ bquc class =post_quotes>的
指向

我通过使用链接表来利用Sql server数据库，mdb'可以做任何事情ADP'（Access Projects）。从那时起多年来，

在评估ADP构建的有用性时，我仍然有时会考虑这个陈述。拉里和我讨论了这种技术

和

他发现它可信。 （希望你不要介意我引用你的先生）所以

地狱......这就是 - 这是给你所有你死的ADP人（和gals

当然）。我知道关于手头的主题已经有很长时间的争论，有些我已经阅读并且是参与者......也许

这个

使用建议甚至浮出水面 - 然而，我觉得以前没有提到
拉里回应的方式。

自A2K诞生以来与ADP合作，我发现很多适合我的优点......但你怎么样？请理解，这个
主题并不是一个公开邀请来抨击ADP'（让我们尝试一下
new），而是一种建设性的方法来弄清楚人们正在使用什么技巧
使他们有价值 - 好？所以，没有进一步的延迟......这是
我的包中的一个创新技巧，我为自己保留了一些时间......如果它对你来说是新的，你可以免费获得。 ..

请注意，ADP使用OLEDB连接连接到Sql Server。这个

类型

的连接可以并且肯定会超出本地

网络，

实际上它可以跨越任何具有端口1433（Sql Server）

打开

并运行Sql Server / MSDE的IP地址。在

中，ADP的最大优势

我的业务是我可以将它们部署到多个位置，同时
托管数据库。按月收费，客户获得托管数据库，
不会产生服务器费用。该模型简单地适合小

分支

办公场景像手套一样。然后，使用绑定表格和智能存储过程设计，我有一个非常紧凑，快速的表现（通过
保持记录下来），丰富，信不信由你...一个安全的交付ADE
有多少人拥有使用Sql Server数据库的网站？如果是这样，

做

你知道你很可能用Access作为项目连接到它

和

只要您拥有
凭证，就可以随心所欲地使用数据库吗？大多数（如果不是所有托管Sql数据库的ISP）允许您与企业管理器连接 - 您可以使用这些相同的凭据来连接您的Access副本。使用数据，构建新查询，构建

一些用于维护数据的

表单，将它们部署为构建复杂但基本无功能的基于网页的维护的替代方案系统。

我相信这是AccessXP的新功能，但您知道现在可以

将

多种表格链接到ADP'的？是的，Paradox，dBase，MDB'和任何

ODBC

或OLEDB可访问引擎......仅举几例。如果你有这个需要，请考虑一下。你总是可以从Sql Server链接其中一些，但

现在

它是表视图中的右键单击和链接选项。

无论如何 - 我希望这个主题保持积极态度，并揭示ADP为开发人员提供的一些非常好的功能。

专业回复表示赞赏。

<两点：

我的意图不是打击ADP。并且我不怀疑
ADP的许多功能可以更轻松地通过互联网连接到服务器，但您似乎只是说只有ADP具备此功能。您所描述的关于通过互联网连接服务器的所有内容也可以通过ODBC
和MDB文件来完成。

一个不仅限于链接的Jet查询表只是因为它们使用ODBC / MDB文件。我有一个应用程序使用了好几年，通过互联网连接到我们的SQL Server，发现即使有一个
拨号连接，它是非常实用的。这是一个为小型数据交易提供的应用程序，几乎所有这些都是使用
存储过程和传递完成的。

第二点关注我为什么几年前完全重新设计相同的应用程序以摆脱ODBC并转而使用与Java servlet交谈的HTTP请求。原因是我被网络管理员告知

，让端口1433对互联网开放是一个
巨大的安全问题。当我对新闻组进行一些调查时，几乎一致同意这个意见。如果事实确实如此，那么我想知道如果定义缺乏适当的安全性，那么你所描述的是什么好处。

我同意新版本中链接到SQL Server以外的其他来源的能力是一个很大的优势。当我第一次在A2000中查看它们时，这是我对它们没什么兴趣的主要原因。
-
我没有查看附带的电子邮件帐户/>来自此消息。发送给...
在Hunter dot com的RBrandt

" Jerry Boone" ;写了

很久以前拉里·林森......（希望你不要介意我引用你的先生）

不，我根本不介意，杰里......我很高兴看到一个启发性的技术讨论。


我想知道这是如何符合微软内部人士的明显的当前

协议，MDB-ODBC击败ADP-ADODB - 也许其中一个内部人士

将加入这个讨论。


正如Rick所说，我知道你可以通过互联网与MDB-ODBC连接，但

我从未想过从表演或安全性来看这是实用的。
的观点。一个开放的互联网端口让我感到震惊，因为它显然已经击中了Rick'的管理员朋友，比LAN / WAN上的开放端口风险更大。


根据我的经验，使用MDB-Jet-ODBC的Access客户端在任何程度上都不依赖于Jet

安全性;它是提供

安全性的服务器数据库。我工作了几年的主要应用程序有一个

Access 2.0客户端 - 没有MDE和安全性，有足够大的空间来驱动

货运列车通过 - 但Informix服务器安全性非常好。


Larry Linson

Microsoft Access MVP

A long time ago Larry Linson (MVP contributor to this group) made a point to
me that mdb''s could do anything ADP''s (Access Projects) could by using
linked tables to leverage Sql server databases. It''s been years since then,
and I still sometimes think about that statement when evaluating the
usefulness of the ADP''s I build. Larry and I discussed this technique and
he found it "Credible" (hope you don''t mind me quoting you sir) so what the
hell... here it goes - this is for all you die-hard ADP guys (and gals of
course). I know there have been long, drawn out debates over the very
subject at hand, some I have read and been a participant... and perhaps this
recommendation of usage has even came to surface - however, I felt it had
not been mentioned before by the way Larry responded.

After working with ADP''s since the birth of A2K, I have found many
advantages that suit me... but what about you? Please understand, this
thread is not an open invitation to bash ADP''s (let''s try something new),
but rather a constructive way to figure out what tricks people are using
that make them "valuable" - ok? So, without further delay... here is one
innovative trick out of my bag in which I have kept for myself for some
time... yours for free if it''s new to you...

Note that ADP''s connect to Sql Server using an OLEDB connection. This type
of connection can and will definitely span further than the local network,
in fact it can span to any IP Address that has port 1433 (Sql Server) open
and Sql Server/MSDE running. Perhaps the strongest advantage ADP''s have in
my business is that I can deploy them to multiple locations while hosting
the database. For a monthly fee, customers get a managed database and do
not incur the expense of a server. This model simply fits the small branch
office scenario "like a glove". Then, using bound forms and intelligent
Stored Procedure design, I have a very tight, fast performing (by keeping
records down), rich, and believe it or not... a secure delivered ADE
application.

How many people have a website that uses a Sql Server database? If so, did
you know you can more than likely connect to it with Access as a Project and
do whatever you want with the database... as long as you have the
credentials? Most, if not all ISP''s who host Sql Databases allow you to
connect with Enterprise Manager - you can use those same credentials to
connect your copy of Access. Work with Data, build new queries, build some
forms for maintaining data, deploy them as an alternative to building
complex, yet featureless web page based maintenance systems.

I believe this is new with AccessXP, but did you know that you can now link
many flavors of tables to ADP''s? Yes, Paradox, dBase, MDB''s, and any ODBC
or OLEDB accessible engine... to name a few. Look into it if you have a
need for this. You could always link some of these from Sql Server, but now
it''s a right click and link option in table view.

Anyway - I hope this thread stays positive and uncovers some really good
features that ADP''s provide to working developers.

Professional replies are appreciated.

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access

解决方案

"Jerry Boone" <je***@antech.biz.killspam> wrote in message
news:f0*******************@newssvr11.news.prodigy. com...

A long time ago Larry Linson (MVP contributor to this group) made a point to me that mdb''s could do anything ADP''s (Access Projects) could by using
linked tables to leverage Sql server databases. It''s been years since then, and I still sometimes think about that statement when evaluating the
usefulness of the ADP''s I build. Larry and I discussed this technique and he found it "Credible" (hope you don''t mind me quoting you sir) so what the hell... here it goes - this is for all you die-hard ADP guys (and gals of
course). I know there have been long, drawn out debates over the very
subject at hand, some I have read and been a participant... and perhaps this recommendation of usage has even came to surface - however, I felt it had
not been mentioned before by the way Larry responded.

After working with ADP''s since the birth of A2K, I have found many
advantages that suit me... but what about you? Please understand, this
thread is not an open invitation to bash ADP''s (let''s try something new),
but rather a constructive way to figure out what tricks people are using
that make them "valuable" - ok? So, without further delay... here is one
innovative trick out of my bag in which I have kept for myself for some
time... yours for free if it''s new to you...

Note that ADP''s connect to Sql Server using an OLEDB connection. This type of connection can and will definitely span further than the local network, in fact it can span to any IP Address that has port 1433 (Sql Server) open and Sql Server/MSDE running. Perhaps the strongest advantage ADP''s have in my business is that I can deploy them to multiple locations while hosting
the database. For a monthly fee, customers get a managed database and do
not incur the expense of a server. This model simply fits the small branch office scenario "like a glove". Then, using bound forms and intelligent
Stored Procedure design, I have a very tight, fast performing (by keeping
records down), rich, and believe it or not... a secure delivered ADE
application.

How many people have a website that uses a Sql Server database? If so, did you know you can more than likely connect to it with Access as a Project and do whatever you want with the database... as long as you have the
credentials? Most, if not all ISP''s who host Sql Databases allow you to
connect with Enterprise Manager - you can use those same credentials to
connect your copy of Access. Work with Data, build new queries, build some forms for maintaining data, deploy them as an alternative to building
complex, yet featureless web page based maintenance systems.

I believe this is new with AccessXP, but did you know that you can now link many flavors of tables to ADP''s? Yes, Paradox, dBase, MDB''s, and any ODBC or OLEDB accessible engine... to name a few. Look into it if you have a
need for this. You could always link some of these from Sql Server, but now it''s a right click and link option in table view.

Anyway - I hope this thread stays positive and uncovers some really good
features that ADP''s provide to working developers.

Professional replies are appreciated.

Two points:

My intent is not to "bash ADPs" and I don''t doubt that many features of an
ADP make connection to a server over the internet easier, but you seem to
be saying that only ADPs have this ability. Everything you''re describing
about connecting to a server over the internet can also be done with ODBC
and an MDB file.

One is not limited to Jet queries over linked tables just because they are
using an ODBC/MDB file. I had an app in use for several years that
connected to our SQL Server over the internet and found that even with a
dial-up connection that it was quite usable. That was an app that lent
itself to small data transactions and nearly all of it was done using
Stored Procedures and Pass-Throughs.

Point two is concerned with why I had to completely redesign that same app
a couple of years ago to get away from ODBC and switch to using HTTP
requests talking to Java servlets. The reason being that I was informed by
our networking admin that leaving port 1433 open to the internet was a huge
security problem. This opinion was nearly unanimously agreed upon when I
made some Newsgroup inquiries about it. If that is in fact true then I
wonder what benefit there is to what you''re describing if it will by
definition be lacking proper security.

I agree that the ability in newer versions to link to sources other than
SQL Server is a big plus. That was the primary reason I had little
interest in them when I first looked at them in A2000.
--
I don''t check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Thanks Rick - very professional. My answers to your respectable points are
these...

Connecting and deploying with ADP''s...
File-Connection-Fill in parameters
At this point all Sql objects are local to the IDE for design change and
will reflect design changes made to the database without updating the ADE.
The database name can be changed any time to connect to a different database
using the connection parameters. For instance, the same accounting system
has 4 different companies with identical database structure, the user can
pick which company by changing this one option and the ADP will adhere
everything across the board.

Connecting and deploying with Jet...
Devise ini or reg entry to create dsn in ODBC with parameters
Start Linking tables
At this point linked tables are there, but the tables must be relinked and
possibly re-deployment of the mdb (remote location and options are limited)
if updates are done on the tables. The database name needs to be fixed, or
else more code and efforts must be installed.

My intent is to make nothing local but the code and Access objects. Also...
local storage, I use local xml and atdg files that update once on app start
for that - works great.

Security - *"A number of industry pundits (and I) feel that Jet security is
an oxymoron. It seems that there are dozens of ways to crack Jet database
security -- there are even some Web sites that will do it for a small fee.
If you''re concerned with security, switch to MSDE or SQL Server where you
will be confronted with another whole set of security issues, but where it
is a whole lot easier to maintain overall security of your database." The
issues he mentions are concerning the overwhelming amount of choices. By
what he has written, I would say that using Jet makes SQL Server less
secure.

Sql Server port 1433 has had one security incident that was made known. My
systems were never effected by it for two reasons -- I only permit 1433 to
clients with static ip''s (reputable businesses) and enter them into my
firewall. On more secure systems, I shift the port as well as work the
firewall specifics. Security is not for the novice - it''s an evolutionary
phenomenon that changes as technology does. What was a unsafe yesterday, is
safe or at least safer today. These questions should be evaluated
periodically, not just once.

The linking of databases was possible before within Sql Server in 7.0.
* From William Vaughn''s latest book on ADO best practices - page 41, last
paragraph.

--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:bt************@ID-98015.news.uni-berlin.de...

"Jerry Boone" <je***@antech.biz.killspam> wrote in message
news:f0*******************@newssvr11.news.prodigy. com...

A long time ago Larry Linson (MVP contributor to this group) made a point

to

me that mdb''s could do anything ADP''s (Access Projects) could by using
linked tables to leverage Sql server databases. It''s been years since then,

and I still sometimes think about that statement when evaluating the
usefulness of the ADP''s I build. Larry and I discussed this technique

and

he found it "Credible" (hope you don''t mind me quoting you sir) so what

the

hell... here it goes - this is for all you die-hard ADP guys (and gals

of course). I know there have been long, drawn out debates over the very
subject at hand, some I have read and been a participant... and perhaps

this

recommendation of usage has even came to surface - however, I felt it had not been mentioned before by the way Larry responded.

After working with ADP''s since the birth of A2K, I have found many
advantages that suit me... but what about you? Please understand, this
thread is not an open invitation to bash ADP''s (let''s try something new), but rather a constructive way to figure out what tricks people are using
that make them "valuable" - ok? So, without further delay... here is one innovative trick out of my bag in which I have kept for myself for some
time... yours for free if it''s new to you...

Note that ADP''s connect to Sql Server using an OLEDB connection. This

type

of connection can and will definitely span further than the local

network,

in fact it can span to any IP Address that has port 1433 (Sql Server)

open

and Sql Server/MSDE running. Perhaps the strongest advantage ADP''s have

in

my business is that I can deploy them to multiple locations while hosting the database. For a monthly fee, customers get a managed database and do not incur the expense of a server. This model simply fits the small

branch

office scenario "like a glove". Then, using bound forms and intelligent
Stored Procedure design, I have a very tight, fast performing (by keeping records down), rich, and believe it or not... a secure delivered ADE
application.

How many people have a website that uses a Sql Server database? If so,

did

you know you can more than likely connect to it with Access as a Project

and

do whatever you want with the database... as long as you have the
credentials? Most, if not all ISP''s who host Sql Databases allow you to
connect with Enterprise Manager - you can use those same credentials to
connect your copy of Access. Work with Data, build new queries, build

some

forms for maintaining data, deploy them as an alternative to building
complex, yet featureless web page based maintenance systems.

I believe this is new with AccessXP, but did you know that you can now

link

many flavors of tables to ADP''s? Yes, Paradox, dBase, MDB''s, and any

ODBC

or OLEDB accessible engine... to name a few. Look into it if you have a
need for this. You could always link some of these from Sql Server, but

now

it''s a right click and link option in table view.

Anyway - I hope this thread stays positive and uncovers some really good
features that ADP''s provide to working developers.

Professional replies are appreciated.

Two points:

My intent is not to "bash ADPs" and I don''t doubt that many features of an
ADP make connection to a server over the internet easier, but you seem to
be saying that only ADPs have this ability. Everything you''re describing
about connecting to a server over the internet can also be done with ODBC
and an MDB file.

One is not limited to Jet queries over linked tables just because they are
using an ODBC/MDB file. I had an app in use for several years that
connected to our SQL Server over the internet and found that even with a
dial-up connection that it was quite usable. That was an app that lent
itself to small data transactions and nearly all of it was done using
Stored Procedures and Pass-Throughs.

Point two is concerned with why I had to completely redesign that same app
a couple of years ago to get away from ODBC and switch to using HTTP
requests talking to Java servlets. The reason being that I was informed

by our networking admin that leaving port 1433 open to the internet was a huge security problem. This opinion was nearly unanimously agreed upon when I
made some Newsgroup inquiries about it. If that is in fact true then I
wonder what benefit there is to what you''re describing if it will by
definition be lacking proper security.

I agree that the ability in newer versions to link to sources other than
SQL Server is a big plus. That was the primary reason I had little
interest in them when I first looked at them in A2000.
--
I don''t check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

"Jerry Boone" wrote

A long time ago Larry Linson ... (hope you
don''t mind me quoting you sir)

No, I don''t mind at all, Jerry... I''m happy to see an enlightening technical
discussion.

I''m wondering how this fits with the Microsoft insiders'' apparent current
agreement that "MDB-ODBC beats ADP-ADODB" -- maybe one of those insiders
will join in this discussion.

As Rick said, I knew you _could_ connect via the Internet with MDB-ODBC, but
I never thought it was practical from either a performance or a security
point of view. An open port to the Internet strikes me, as it apparently
struck Rick''s admin friend, as a lot riskier than an open port on a LAN/WAN.

In my experience, Access clients using MDB-Jet-ODBC do not rely on Jet
security to any degree; it is the server database that provides the
security. A major app on which I worked off and on for several years had an
Access 2.0 client -- no MDE and security with a hole big enough to drive a
freight train through -- but the Informix server security was pretty good.

Larry Linson
Microsoft Access MVP

这篇关于使用ADP的一个很好的理由的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！