ADP与MDB：速度 [英] ADP vs. MDB: Speed
问题描述
我有一个带有ODBC链接视图的情况，在Access 2000 MDB中有一个SQL
7后端。视图滚动速度非常慢。但是，如果我在ADP文件中打开视图
，它会快速滚动。
我需要为视图使用ODBC链接，因为它需要可编辑。
否则，我会使用传递查询。
在之前关于使用MDB文件与ADP文件作为对于SQL Server来说，我得到的印象是两者大致相同，但是这个MDB是一种比较成熟的技术而且问题比/>
ADP技术。然而，我对这个视图的ADP文件
注意到的速度差异很大，并且非常令人不安。使用
一个MDB文件。
任何想法/意见/建议将不胜感激。我已经在下面复制了
视图的SQL以供参考。
谢谢，
Neil
SQL查询问题：
SELECT INVTRY。[Index]，INVTRY.TITLE，INVTRY.AUTHILL1，
INVTRY.attFirstEdition，INVTRY.attSigned，
ISNULL（INVTRY.attSignedPD，''''）SignedCond，INVTRY.YRPUB，
INVTRY.PRICE，INVTRY。 Web，INVTRY.Status，
INVTRY.WebStatusPending，INVTRY.ActivateDate，
INVTRY.DeactivateDate，INVTRY.WebAddedBatchID，
INVTRY.AllowDuplicate， INVTRY.WebAction，
INVTRY.WebActionPending，INVTRY.DateModified，
INVTRY.DateWebActionApplied，INVTRY.JIT，INVTRY.MImage，
INVTRY。 HImage，INVTRY.AdCode，
CASE WHEN INVURN.WebAddedBatchID IS NOT NULL
THEN - 1 ELSE 0 END as OnWeb
FROM vwInventory_Dupes INNER JOIN
（WebStatus INNER JOIN
（INVOND INNER JOIN
tabStatus ON INVTRY.Status = ta bStatus.Status）ON
WebStatus.WebStatus = INVTRY.Web）ON
（vwInventory_Dupes.YearPub = INVTRY.YRPUB）AND
（vwInventory_Dupes .SignedCond = ISNULL（INVTRY.attSignedPD，
''''）AND（vwInventory_Dupes.Signed = INVTRY.attSigned）AND
（vwInventory_Dupes.FirstEd = INVTRY.attFirstEdition ）和
（vwInventory_Dupes.Author = INVTRY.AUTHILL1）和
（vwInventory_Dupes.TITLE = INVTRY.TITLE）
WHERE（（（tabStatus） .ForWeb）= 1）AND（（WebStatus.IncludeDupe）
= 1））
用于vwInventory_Dupes的SQL，用作子查询：
SELECT INVTRY.TITLE，INVTRY.AUTHILL1作者，
Cast（attFirstEdition AS tinyint）FirstEd，
Cast（attSigned AS tinyint）签名，
ISNULL（INVTRY.attSignedPD，''''）SignedCond，
INVTRY.YRPUB YearPub
来自WebStatus INNER JOIN
（INVOND INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status）ON
WebStatus.WebStatus = INVTRY.Web
WHERE（（（tabStatus.ForWeb）= 1）AND（（WebStatus.IncludeDupe）
= 1））
GROUP BY INVTRY.TITLE，INVTRY.AUTHILL1，
Cast（attFirstEdition AS tinyint），Cast（attSigned AS tinyint），
ISNULL（INVTRY .attSignedPD，''''，INVTRY.YRPUB
HAVING（（（COUNT（INVTRY。[INDEX]））> 1））
I have a situation with an ODBC linked view in an Access 2000 MDB with a SQL
7 back end. The view is scrolling very slowly. However, if I open the view
in an ADP file, it scrolls quickly.
I needed to use an ODBC link for the view because it needs to be editable.
Otherwise, I would have used a pass-through query.
In previous discussions about using an MDB file vs. an ADP file as a front
end for SQL Server, the impression I got was that both were about the same,
but that the MDB was a more mature technology and less problematic than the
ADP technology. However, the speed difference I''m noticing with the ADP file
in regards to this view is significant and is very disconcerting re. using
an MDB file.
Any thoughts/comments/suggestions would be appreciated. I''ve reproduced the
view''s SQL below for reference.
Thanks,
Neil
SQL for view in question:
SELECT INVTRY.[Index], INVTRY.TITLE, INVTRY.AUTHILL1,
INVTRY.attFirstEdition, INVTRY.attSigned,
ISNULL(INVTRY.attSignedPD, '' '') SignedCond, INVTRY.YRPUB,
INVTRY.PRICE, INVTRY.Web, INVTRY.Status,
INVTRY.WebStatusPending, INVTRY.ActivateDate,
INVTRY.DeactivateDate, INVTRY.WebAddedBatchID,
INVTRY.AllowDuplicate, INVTRY.WebAction,
INVTRY.WebActionPending, INVTRY.DateModified,
INVTRY.DateWebActionApplied, INVTRY.JIT, INVTRY.MImage,
INVTRY.HImage, INVTRY.AdCode,
CASE WHEN INVTRY.WebAddedBatchID IS NOT NULL
THEN - 1 ELSE 0 END AS OnWeb
FROM vwInventory_Dupes INNER JOIN
(WebStatus INNER JOIN
(INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status) ON
WebStatus.WebStatus = INVTRY.Web) ON
(vwInventory_Dupes.YearPub = INVTRY.YRPUB) AND
(vwInventory_Dupes.SignedCond = ISNULL(INVTRY.attSignedPD,
'' '')) AND (vwInventory_Dupes.Signed = INVTRY.attSigned) AND
(vwInventory_Dupes.FirstEd = INVTRY.attFirstEdition) AND
(vwInventory_Dupes.Author = INVTRY.AUTHILL1) AND
(vwInventory_Dupes.TITLE = INVTRY.TITLE)
WHERE (((tabStatus.ForWeb) = 1) AND ((WebStatus.IncludeDupe)
= 1))
SQL for vwInventory_Dupes, used as subquery:
SELECT INVTRY.TITLE, INVTRY.AUTHILL1 Author,
Cast(attFirstEdition AS tinyint) FirstEd,
Cast(attSigned AS tinyint) Signed,
ISNULL(INVTRY.attSignedPD, '' '') SignedCond,
INVTRY.YRPUB YearPub
FROM WebStatus INNER JOIN
(INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status) ON
WebStatus.WebStatus = INVTRY.Web
WHERE (((tabStatus.ForWeb) = 1) AND ((WebStatus.IncludeDupe)
= 1))
GROUP BY INVTRY.TITLE, INVTRY.AUTHILL1,
Cast(attFirstEdition AS tinyint), Cast(attSigned AS tinyint),
ISNULL(INVTRY.attSignedPD, '' ''), INVTRY.YRPUB
HAVING (((COUNT(INVTRY.[INDEX])) > 1))
推荐答案
ADP和MDB使用记录集的方式是非常不同的，所以有时一个或
另一个将更快。
默认情况下，MDB打开一个动态集，这意味着它首先打开一个连接到
获取记录的密钥列表，然后读取所需的实际记录
用于显示，通过单独选择10条记录显式密钥。这个
可以帮助提高每行有大量数据的速度，因为只有实际查看过的行才会被读取，而不是全部。另一方面，如果表格
的行数非常多，Access将花费大量时间在
后台读取整个键列表，并且如果由于某种原因每行的键查找
很慢，一切都会很迟钝。
ADP，通常使用静态记录集，以及绝对上限为10,000
行是应用的，所以如果你的记录集有更多，你就不会得到
所有行。静态意味着一次加载所有数据，然后通过它在memeory中浏览
。加载数据后速度非常快，但如果每个行b / b $ b行有大量数据，尤其是备注字段等，则可能需要很长时间
时间最初加载。
On Sun，2005年3月20日08:31:48 GMT，Neil < NJ **** @ pxdy.com>写道：
The ways ADPs and MDBs use recordsets are very different, so sometimes one or
the other will be faster.
By default, the MDB opens a Dynaset which means it first opens a connection to
grab the list of keys for the records, then reads the actual records as needed
for display by doing individual selects of 10 records aby explicit key. This
can help speed when each row has a lot of data because only the rows that are
actually viewd will be read, not all of them. On the other hand, if the table
has a very large number of rows, Access will spend a lot of time in the
background reading the whole list of keys, and if the key lookup for each row
is slow for some reason, everything will be sluggish.
An ADP, a static recordset is normally used, and an absolute cap of 10,000
rows is applied, so if your recordset has more than that, you just won''t get
all the rows. Static means in loads all the data at once, then you browse
through it in memeory. That''s very fast once you load the data, but if each
row has a lot of data, especially memo fields and such, it can take a long
time to initially load.
On Sun, 20 Mar 2005 08:31:48 GMT, "Neil" <nj****@pxdy.com> wrote:
我有一个带有ODBC链接视图的情况，在Access 2000 MDB中有一个SQL后端。视图滚动速度非常慢。但是，如果我在ADP文件中打开视图
，它会快速滚动。
我需要为视图使用ODBC链接，因为它需要是可编辑的。
否则，我会使用传递查询。
在之前关于使用MDB文件与ADP文件作为SQL Server前端的讨论中，我得到的印象是两者大致相同，但是MDB是一种更成熟的技术，并且比
ADP技术更少问题。但是，我对这个视图的ADP文件注意到的速度差异很大，并且非常令人不安。使用
MDB文件。
任何想法/意见/建议将不胜感激。我已经在下面复制了
视图的SQL以供参考。
谢谢，
Neil
用于查看的SQL问题：
SELECT INVTRY。[Index]，INVTRY.TITLE，INVTRY.AUTHILL1，
INVTRY.attFirstEdition，INVTRY.attSigned，
ISNULL（INVTRY.attSignedPD，''' '）SignedCond，INVTRY.YRPUB，
INVTRY.PRICE，INVTRY.Web，INVTRY.Status，
INVTRY.WebStatusPending，INVTRY.ActivateDate，
INVTRY.DeactivateDate，INVTRY.WebAddedBatchID，
INVTRY.AllowDuplicate，INVTRY.WebAction，
INVTRY.WebActionPending，INVTRY.DateModified，
INVTRY.DateWebActionApplied，INVTRY.JIT，INVTRY.MImage，
INVTRY.HImage，INVTRY.AdCode，
当INVTRY.WebAddedBatchID不为空时的情况
然后 - 1结束0结束OnWeb
来自vwInventory_Dupes INNER JOIN
（WebStatus INNER JOIN
（INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status）ON
WebStatus.WebStatus = INVTRY.Web）ON
（vwInventory_Dupes.YearPub = INVTRY.YRPUB）AND
（vwInventory_Dupes.SignedCond = ISNULL（INVTRY.attSignedPD，
'''））AND（vwInventory_Dupes.Signed = INVTRY.attSigned）AND
（vwInventory_Dupes.FirstEd = INVTRY.attFirstEdition）AND
（vwInventory_Dupes.Author = INVTRY.AUTHILL1）AND
（vwInventory_Dupes.TITLE = INVTRY.TITLE）
WHERE（（tabStatus.ForWeb ）= 1）AND（（WebStatus.IncludeDupe）
= 1））
用于vwInventory_Dupes的SQL，用作子查询：
SELECT INVTRY.TITLE，INVTRY。 AUTHILL1作者，
演员（attFirstEdition AS tinyint）FirstEd，
演员（attSigned AS tinyint）签名，
ISNULL（INVTRY.attSignedPD，'''）SignedCond，
INVTRY。 YRPUB YearPub
来自WebStatus INNER JOIN
（INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status）ON
WebStatus.WebStatus = INVTRY.Web
WHERE（ （（tabStatus.ForWeb）= 1）AND（（WebStatus.IncludeDupe）
= 1））
GROUP BY INVTRY.TITLE，INVTRY.AUTHILL1，
Cast（attFirstEdition AS tinyint），Cast（attSigned AS tinyint），
ISNULL（INVTRY.attSignedPD，''''），INVTRY.YRPUB
HAVING（（（COUNT（INVTRY。[INDEX]））> 1））
I have a situation with an ODBC linked view in an Access 2000 MDB with a SQL
7 back end. The view is scrolling very slowly. However, if I open the view
in an ADP file, it scrolls quickly.
I needed to use an ODBC link for the view because it needs to be editable.
Otherwise, I would have used a pass-through query.
In previous discussions about using an MDB file vs. an ADP file as a front
end for SQL Server, the impression I got was that both were about the same,
but that the MDB was a more mature technology and less problematic than the
ADP technology. However, the speed difference I''m noticing with the ADP file
in regards to this view is significant and is very disconcerting re. using
an MDB file.
Any thoughts/comments/suggestions would be appreciated. I''ve reproduced the
view''s SQL below for reference.
Thanks,
Neil
SQL for view in question:
SELECT INVTRY.[Index], INVTRY.TITLE, INVTRY.AUTHILL1,
INVTRY.attFirstEdition, INVTRY.attSigned,
ISNULL(INVTRY.attSignedPD, '' '') SignedCond, INVTRY.YRPUB,
INVTRY.PRICE, INVTRY.Web, INVTRY.Status,
INVTRY.WebStatusPending, INVTRY.ActivateDate,
INVTRY.DeactivateDate, INVTRY.WebAddedBatchID,
INVTRY.AllowDuplicate, INVTRY.WebAction,
INVTRY.WebActionPending, INVTRY.DateModified,
INVTRY.DateWebActionApplied, INVTRY.JIT, INVTRY.MImage,
INVTRY.HImage, INVTRY.AdCode,
CASE WHEN INVTRY.WebAddedBatchID IS NOT NULL
THEN - 1 ELSE 0 END AS OnWeb
FROM vwInventory_Dupes INNER JOIN
(WebStatus INNER JOIN
(INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status) ON
WebStatus.WebStatus = INVTRY.Web) ON
(vwInventory_Dupes.YearPub = INVTRY.YRPUB) AND
(vwInventory_Dupes.SignedCond = ISNULL(INVTRY.attSignedPD,
'' '')) AND (vwInventory_Dupes.Signed = INVTRY.attSigned) AND
(vwInventory_Dupes.FirstEd = INVTRY.attFirstEdition) AND
(vwInventory_Dupes.Author = INVTRY.AUTHILL1) AND
(vwInventory_Dupes.TITLE = INVTRY.TITLE)
WHERE (((tabStatus.ForWeb) = 1) AND ((WebStatus.IncludeDupe)
= 1))
SQL for vwInventory_Dupes, used as subquery:
SELECT INVTRY.TITLE, INVTRY.AUTHILL1 Author,
Cast(attFirstEdition AS tinyint) FirstEd,
Cast(attSigned AS tinyint) Signed,
ISNULL(INVTRY.attSignedPD, '' '') SignedCond,
INVTRY.YRPUB YearPub
FROM WebStatus INNER JOIN
(INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status) ON
WebStatus.WebStatus = INVTRY.Web
WHERE (((tabStatus.ForWeb) = 1) AND ((WebStatus.IncludeDupe)
= 1))
GROUP BY INVTRY.TITLE, INVTRY.AUTHILL1,
Cast(attFirstEdition AS tinyint), Cast(attSigned AS tinyint),
ISNULL(INVTRY.attSignedPD, '' ''), INVTRY.YRPUB
HAVING (((COUNT(INVTRY.[INDEX])) > 1))
您可以尝试在链接视图上添加虚拟索引：
http://support.microsoft.com/kb/q209123/
如果这没有用，那么你将不得不使用一个未绑定的表格加上
SQL传递查询（或ADO对象）来解决你的速度问题
MDB。另一种解决方案可能是使用TS来模拟高速局域网。
我不知道你在哪里得到的印象是MDB与
大致相同
ADP的速度。多次重复使用MDB''链接表和视图的使用
只是快速Lan上小型
数据库的可行解决方案。 />
SL
" Neil" < NJ **** @ pxdy.com>在消息中写道
新闻：Ux ******************* @ newsread1.news.pas.eart hlink.net ...
You may try to add a virtual index on your linked view:
http://support.microsoft.com/kb/q209123/
If this doesn''t help, then you will have to use an unbound form coupled with
SQL pass-through queries (or ADO objects) to resolve your speed problem with
MDB. Another solution could be to go with TS to simulate a high-speed LAN.
I don''t know where you got the impression that MDB were about the same as
ADP in term of speed. It has been repeated a number of times that the use
of MDB'' linked tables and views is only a workable solution for small
databases on a fast Lan.
S. L.
"Neil" <nj****@pxdy.com> wrote in message
news:Ux*******************@newsread1.news.pas.eart hlink.net...
我在Access 2000 MDB中使用带有SQL 7后端的ODBC链接视图。视图滚动速度非常慢。但是，如果我在ADP文件中打开
视图，它会快速滚动。
我需要为视图使用ODBC链接，因为它需要可编辑。
否则，我会使用传递查询。
在之前关于使用MDB文件与ADP文件作为SQL Server前端的讨论中，我得到的印象是两者都是相同的，但MDB是一种比ADP技术更成熟的技术，而且问题更少。但是，我对这个视图的ADP文件注意到的速度差异很大，并且非常令人不安。使用MDB文件。
任何想法/意见/建议将不胜感激。我已经在下面复制了以下视图的SQL供参考。
谢谢，
Neil
用于查看的SQL问题：
SELECT INVTRY。[Index]，INVTRY.TITLE，INVTRY.AUTHILL1，
INVTRY.attFirstEdition，INVTRY.attSigned，
ISNULL（INVTRY.attSignedPD，''' '）SignedCond，INVTRY.YRPUB，
INVTRY.PRICE，INVTRY.Web，INVTRY.Status，
INVTRY.WebStatusPending，INVTRY.ActivateDate，
INVTRY.DeactivateDate，INVTRY.WebAddedBatchID，
INVTRY.AllowDuplicate，INVTRY.WebAction，
INVTRY.WebActionPending，INVTRY.DateModified，
INVTRY.DateWebActionApplied，INVTRY.JIT，INVTRY.MImage，
INVTRY.HImage，INVTRY.AdCode，
当INVTRY.WebAddedBatchID不为空时的情况
然后 - 1结束0结束OnWeb
来自vwInventory_Dupes INNER JOIN
（WebStatus INNER JOIN
（INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status）ON
WebStatus.WebStatus = INVTRY.Web） ON
（vwInventory_Dupes.YearPub = INVTRY.YRPUB）AND
（vwInventory_Dupes.SignedCond = ISNULL（INVTRY.attSignedPD，
'''））AND（vwInventory_Dupes.Signed = INVTRY.attSigned） AND
（vwInventory_Dupes.FirstEd = INVTRY.attFirstEdition）AND
（vwInventory_Dupes.Author = INVTRY.AUTHILL1）AND
（vwInventory_Dupes.TITLE = INVTRY.TITLE）
WHERE（（（ tabStatus.ForWeb）= 1）AND（（WebStatus.IncludeDupe）
= 1））
用于vwInventory_Dupes的SQL，用作子查询：
SELECT INVTRY.TITLE ，INVTRY.AUTHILL1作者，
演员（attFirstEdition AS tinyint）FirstEd，
演员（attSigned AS tinyint）签名，
ISNULL（INVTRY.attSignedPD，'''）SignedCond， INVTRY.YRPUB YearPub
来自WebStatus INNER JOIN
（INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status）ON
WebStatus.WebStatus = INVTRY.Web
WHERE（（（tabStatus.ForWeb）= 1）AND（（WebStatus.IncludeDupe）
= 1））
GROUP BY INVTRY.TITLE，INVTRY.AUTHILL1，
Cast（attFirstEdition AS tinyint），Cast（attSigned AS tinyint），
ISNULL（INVTRY.attSignedPD，'''' ），INVTRY.YRPUB
HAVING（（（COUNT（INVTRY。[INDEX]））> 1））
I have a situation with an ODBC linked view in an Access 2000 MDB with a
SQL 7 back end. The view is scrolling very slowly. However, if I open the
view in an ADP file, it scrolls quickly.
I needed to use an ODBC link for the view because it needs to be editable.
Otherwise, I would have used a pass-through query.
In previous discussions about using an MDB file vs. an ADP file as a front
end for SQL Server, the impression I got was that both were about the
same, but that the MDB was a more mature technology and less problematic
than the ADP technology. However, the speed difference I''m noticing with
the ADP file in regards to this view is significant and is very
disconcerting re. using an MDB file.
Any thoughts/comments/suggestions would be appreciated. I''ve reproduced
the view''s SQL below for reference.
Thanks,
Neil
SQL for view in question:
SELECT INVTRY.[Index], INVTRY.TITLE, INVTRY.AUTHILL1,
INVTRY.attFirstEdition, INVTRY.attSigned,
ISNULL(INVTRY.attSignedPD, '' '') SignedCond, INVTRY.YRPUB,
INVTRY.PRICE, INVTRY.Web, INVTRY.Status,
INVTRY.WebStatusPending, INVTRY.ActivateDate,
INVTRY.DeactivateDate, INVTRY.WebAddedBatchID,
INVTRY.AllowDuplicate, INVTRY.WebAction,
INVTRY.WebActionPending, INVTRY.DateModified,
INVTRY.DateWebActionApplied, INVTRY.JIT, INVTRY.MImage,
INVTRY.HImage, INVTRY.AdCode,
CASE WHEN INVTRY.WebAddedBatchID IS NOT NULL
THEN - 1 ELSE 0 END AS OnWeb
FROM vwInventory_Dupes INNER JOIN
(WebStatus INNER JOIN
(INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status) ON
WebStatus.WebStatus = INVTRY.Web) ON
(vwInventory_Dupes.YearPub = INVTRY.YRPUB) AND
(vwInventory_Dupes.SignedCond = ISNULL(INVTRY.attSignedPD,
'' '')) AND (vwInventory_Dupes.Signed = INVTRY.attSigned) AND
(vwInventory_Dupes.FirstEd = INVTRY.attFirstEdition) AND
(vwInventory_Dupes.Author = INVTRY.AUTHILL1) AND
(vwInventory_Dupes.TITLE = INVTRY.TITLE)
WHERE (((tabStatus.ForWeb) = 1) AND ((WebStatus.IncludeDupe)
= 1))
SQL for vwInventory_Dupes, used as subquery:
SELECT INVTRY.TITLE, INVTRY.AUTHILL1 Author,
Cast(attFirstEdition AS tinyint) FirstEd,
Cast(attSigned AS tinyint) Signed,
ISNULL(INVTRY.attSignedPD, '' '') SignedCond,
INVTRY.YRPUB YearPub
FROM WebStatus INNER JOIN
(INVTRY INNER JOIN
tabStatus ON INVTRY.Status = tabStatus.Status) ON
WebStatus.WebStatus = INVTRY.Web
WHERE (((tabStatus.ForWeb) = 1) AND ((WebStatus.IncludeDupe)
= 1))
GROUP BY INVTRY.TITLE, INVTRY.AUTHILL1,
Cast(attFirstEdition AS tinyint), Cast(attSigned AS tinyint),
ISNULL(INVTRY.attSignedPD, '' ''), INVTRY.YRPUB
HAVING (((COUNT(INVTRY.[INDEX])) > 1))
On Sun，2005年3月20日12:32:10 -0500，Sylvain Lafontaine < sylvain aei ca（填空
空白，请不要发送垃圾邮件）>写道：
On Sun, 20 Mar 2005 12:32:10 -0500, "Sylvain Lafontaine" <sylvain aei ca (fill
the blanks, no spam please)> wrote:
您可以尝试在链接视图上添加虚拟索引：
http://support.microsoft.com/kb/q209123/
如果这没有帮助，那么你将拥有使用未绑定的表单与
SQL传递查询（或ADO对象）来解决您的速度问题与
MDB。另一个解决方案可能是使用TS来模拟高速局域网。
我不知道你在哪里得到MDB与
ADP大致相同的印象速度。已多次重复使用MDB''链接表和视图只是快速Lan上小型数据库的可行解决方案。
You may try to add a virtual index on your linked view:
http://support.microsoft.com/kb/q209123/
If this doesn''t help, then you will have to use an unbound form coupled with
SQL pass-through queries (or ADO objects) to resolve your speed problem with
MDB. Another solution could be to go with TS to simulate a high-speed LAN.
I don''t know where you got the impression that MDB were about the same as
ADP in term of speed. It has been repeated a number of times that the use
of MDB'' linked tables and views is only a workable solution for small
databases on a fast Lan.
坦率地说，我觉得这个说法很荒谬。包括我自己在内的许多开发人员使用MDB作为前端到各种SQL
服务器后端已经有很多年了才有这样的事情。 ADP。当
MDB缓慢时，修复它的变通方法远不如ADP中要求的简单使它们在许多情况下起作用的工作方式更加艰巨。
Frankly, I find that statement ludicrous. Many developers including myself
have had excelent results using MDBs as front-ends to various kinds of SQL
Server back-end for many years before there was such a thing as an ADP. When
MDBs are slow, the workarounds to fix it are far less arduous than the
workarounds required in ADPs to simply make them function in many cases.
这篇关于ADP与MDB：速度的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
