在网络上使用带有A97后端的A2000前端时减速 [英] Slowdown when using A2000 frontend with A97 backend on network

问题描述

有没有人注意到这个问题？我将后端转换为A2000

并解决了性能问题。我们提供了97和2000版本的b $ b我们的软件，因此我们将后端保留在A97中，以便为用户进行简单的升级

。我们已经这样做了多年，但是一个新的客户已经有了严重的性能问题......通过将后端转换为
2000来解决。

-

问候，


布拉德利

解决方案

不。我的2个数据库应用程序变得非常快，对于用户来说前端转换为Windows 2000后，b / b
。后端仍然是windows

97，因为有些用户尚未转换。

Galina

" Bradley" <峰; br ***** @ REMOVETHIScomcen.com.au>在消息新闻中写道：< 40 ****** @ nexus.comcen.com.au> ...

有没有人注意到这个问题？我将后端转换为A2000
并解决了性能问题。我们提供了97和2000版本的软件，因此我们将后端保留在A97中，以便为用户进行简单的升级。我们已经这样做了多年，但是一个新的客户已经有严重的性能问题......通过将后端转换为
2000来解决。

各种版本都有性能影响，因为A2000使用JET

4，并且必须将调用转换为JET 3.5以从A97读取数据

后端。点击是显而易见的，但不是戏剧性的。


如果你有严重的话。性能问题，它更可能与需要关闭的A2000中的某些guff相关联。名称自动更正是

的罪魁祸首。由于无法在A97表格上定义

，因此无法修复子数据表。关闭行级锁定也是值得的 - 我们

发现一些并发问题，当A2000试图运行它并且A97返回

end不支持它。


有关A2000性能的一般指导，请参阅：
http://www.granite.ab.ca/access/performancefaq.htm


-

Allen Browne - 微软MVP。西澳大利亚州珀斯。

访问用户提示 - http：// allenbrowne.com/tips.html

回复群组，而不是mvps dot org的allenbrowne。


" Bradley" <峰; br ***** @ REMOVETHIScomcen.com.au>在消息中写道

新闻：40 ****** @ nexus.comcen.com.au ...

有没有人注意到这个问题？我将后端转换为A2000
并解决了性能问题。我们提供了97和2000版本的软件，因此我们将后端保留在A97中，以便为用户进行简单的升级。我们已经这样做了多年，但是一个新的客户已经有严重的性能问题......通过将后端转换为
2000来解决。

Allen Browne写道：

各种版本都有性能影响，因为A2000
使用JET 4，并且调用必须转换为JET 3.5才能读取
数据形成A97后端。点击是显而易见的，但不是戏剧性的。

如果你有严重的话。性能问题，它更可能与A2000中需要关闭的一些guff相关联。名称
自动更正是罪魁祸首。子数据表无法修复，因为它们无法在A97表上定义。关闭行级别锁定也是值得的 - 我们发现一些并发问题当
A2000试图运行它并且A97后端不支持它。

关于一般指导使用A2000的表现，请参阅：
http：// www。 granite.ab.ca/access/performancefaq.htm

Ta。我知道你列出的大部分内容（了解它们是硬

方式:)


它通过转换解决了无论如何要到A2000 :)

-

问候，


布拉德利


"布拉德利和QUOT; <峰; br ***** @ REMOVETHIScomcen.com.au>在消息中写道
新闻：40 ****** @ nexus.comcen.com.au ...

有没有人注意到这个问题？我将后端转换为
A2000并解决了性能问题。我们提供97和2000版本的软件，因此我们将后端保留在A97中，以便为用户简化升级。我们已经这样做了多年，但是一个新的客户端一直有严重的性能问题......通过将后端转换为2000来解决。

-

问候，


布拉德利

Has anyone else noticed this problem? I converted the back-end to A2000
and the performance problem was fixed. We supply a 97 and 2000 version
of our software so we kept the backend in A97 to make upgrading simple
for users. We''ve done it like that for years but a new client has been
having severe performance issues... solved by converting the backend to
2000.
--
regards,

Bradley

解决方案

Nope. My 2 database applications became noticably faster for users
with front-end converted to Windows 2000. Back-end is still windows
97, because some users are not converted yet.
Galina
"Bradley" <br*****@REMOVETHIScomcen.com.au> wrote in message news:<40******@nexus.comcen.com.au>...

Has anyone else noticed this problem? I converted the back-end to A2000
and the performance problem was fixed. We supply a 97 and 2000 version
of our software so we kept the backend in A97 to make upgrading simple
for users. We''ve done it like that for years but a new client has been
having severe performance issues... solved by converting the backend to
2000.

There is a performance hit working across versions, because A2000 uses JET
4, and the calls must be converted to JET 3.5 to read the data form the A97
back end. The hit is noticable, but not dramatic.

If you have "severe" performance issues, it is more likely associated with
some of the guff in A2000 that needs to be turned off. Name AutoCorrect is
the main culprit. Subdatasheets can''t be fixed since they cannot be defined
on the A97 tables. Turning off Row Level locking is also worthwhile - we
found some concurrency issues when A2000 tried to run this and the A97 back
end does not support it.

For general guidance on performance with A2000, see:
http://www.granite.ab.ca/access/performancefaq.htm

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

"Bradley" <br*****@REMOVETHIScomcen.com.au> wrote in message
news:40******@nexus.comcen.com.au...

Has anyone else noticed this problem? I converted the back-end to A2000
and the performance problem was fixed. We supply a 97 and 2000 version
of our software so we kept the backend in A97 to make upgrading simple
for users. We''ve done it like that for years but a new client has been
having severe performance issues... solved by converting the backend to
2000.

Allen Browne wrote:

There is a performance hit working across versions, because A2000
uses JET 4, and the calls must be converted to JET 3.5 to read the
data form the A97 back end. The hit is noticable, but not dramatic.

If you have "severe" performance issues, it is more likely associated
with some of the guff in A2000 that needs to be turned off. Name
AutoCorrect is the main culprit. Subdatasheets can''t be fixed since
they cannot be defined on the A97 tables. Turning off Row Level
locking is also worthwhile - we found some concurrency issues when
A2000 tried to run this and the A97 back end does not support it.

For general guidance on performance with A2000, see:
http://www.granite.ab.ca/access/performancefaq.htm
Ta. I''m aware of most of the things you listed (learned them the "hard"
way:)

It''s solved by converting to A2000 anyway :)
--
regards,

Bradley

"Bradley" <br*****@REMOVETHIScomcen.com.au> wrote in message
news:40******@nexus.comcen.com.au...

Has anyone else noticed this problem? I converted the back-end to
A2000 and the performance problem was fixed. We supply a 97 and 2000
version of our software so we kept the backend in A97 to make
upgrading simple for users. We''ve done it like that for years but a
new client has been having severe performance issues... solved by
converting the backend to 2000.

--
regards,

Bradley

这篇关于在网络上使用带有A97后端的A2000前端时减速的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！