计时器事件不会在Access 2000中触发 [英] Timer Event Won't Fire In Access 2000

问题描述

我有一个使用Access

2000文件格式在Access 2003中编写的数据库。当我在Access 2003中运行mdb时，一切正常工作

罚款。如果我在Access 2000中运行它，则计时器事件不会触发我的

表单。这太疯狂了。有没有人看过这种行为？


任何帮助表示感谢。

解决方案

嗨Wayne。


我不知道Timer事件的具体问题。这听起来更像是某种腐败，可能与A2000

使用与A2003不同的二进制文件（编译代码）有关。


使用A2000，确保未选中以下框：

工具|选项|一般|名称自动更正

然后压缩数据库：

工具|数据库实用程序|压缩

然后在Access未运行时通过在

命令提示符下输入类似的内容来反编译数据库的副本。这是一行，并包括

引号：

" c：\Program Files \ Microsoft Office \ office \ msmscess.exe" /反编译

" c：\ MyPath \ MyDatabase.mdb"

再次压缩。

检查代码是否编译。

查看Timer事件现在是否运行。


-

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

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

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


" Wayne Aprato" < CQ ******* @ volcanomail.com>在消息中写道

新闻：4d ************************* @ posting.google.co m ... < blockquote class =post_quotes>我有一个使用Access
2000文件格式在Access 2003中编写的数据库。当我在Access 2003中运行mdb时，一切正常。如果我在Access 2000中运行它，计时器事件就不会触发我的
表单。这太疯狂了。有没有人见过这种行为？

任何帮助表示赞赏。

Wayne Aprato写道：

I有一个使用Access
2000文件格式在Access 2003中编写的数据库。当我在Access 2003中运行mdb时，一切正常。如果我在Access 2000中运行它，计时器事件就不会触发我的
表单。这太疯狂了。有没有人见过这种行为？

任何帮助表示赞赏。

什么是计时器间隔？您是否将其重置为零？

感谢Allen和Salad的回复，但在尝试您的建议后问题仍然存在。
。继我上一篇文章之后，我已经确定它不是我最初想到的计时器事件。给我带来问题的

表格是类似的。它们基于

查询。其中一个查询字段的条件是表单上的下拉列表

。当从列表中选择一个值时，表单将按该值过滤
。列表的默认值是*。我打开时间为100ms的计时器事件上的
表格。如果这个

没有完成，则值不会显示，因为查询在表单上使用

a字段作为其标准之一。发生故障

使表单打开并且不显示任何记录，何时应该显示所有记录。


我发现了什么，因为我的上一篇文章是数据库工作正常

一个没有任何服务包的Access 2000安装

安装 - 我'我已经在另一台机器上进行了干净的安装尝试了这个。

当安装Access 2000有服务时出现问题

版本1a或更高版本已应用。我通过安装服务包尝试了这个

1a - 问题出现 - 卸载Access 2000并重新安装

没有服务包 - 问题消失了。如前所述，

数据库在Access 2003上运行正常。


我想这个故事的寓意是你想要一个Access 2000数据库，
在Access 2000中写入，而不是Access 2003，即使默认使用Access 2000

文件格式。


如果你有关于导致这种奇怪的行为的任何其他想法，我将不胜感激听到他们。


问候。

I have a database that was written in Access 2003 using the Access
2000 file format. When I run the mdb in Access 2003 everything works
fine. If I run it in Access 2000 the timer event won''t fire on my
forms. This is crazy. Has anyone seen this behaviour?

Any help appreciated.

解决方案

Hi Wayne.

I''m not aware of a specific problem with the Timer event. It sounds more
like some kind of corruption, probably related to the fact that the A2000
uses a different binary (compiled code) than A2003.

Using A2000, make sure the boxes are unchecked under:
Tools | Options | General | Name AutoCorrect
Then compact the database:
Tools | Database Utilities |Compact
Then decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Compact again.
Check that the code compiles.
See if the Timer event runs now.

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

"Wayne Aprato" <cq*******@volcanomail.com> wrote in message
news:4d*************************@posting.google.co m...

I have a database that was written in Access 2003 using the Access
2000 file format. When I run the mdb in Access 2003 everything works
fine. If I run it in Access 2000 the timer event won''t fire on my
forms. This is crazy. Has anyone seen this behaviour?

Any help appreciated.

Wayne Aprato wrote:

I have a database that was written in Access 2003 using the Access
2000 file format. When I run the mdb in Access 2003 everything works
fine. If I run it in Access 2000 the timer event won''t fire on my
forms. This is crazy. Has anyone seen this behaviour?

Any help appreciated.

What is the timer interval? Are you resetting it somewhere to zero?

Thanks for the reply Allen and Salad but the problem still remains
after trying your suggestions. Further to my previous post, I''ve
ascertained that it isn''t the timer event as I first thought. The
forms that are giving me problems are similar. They are based on
queries. The criteria of one of the query fields is a drop down list
on the form. When a value is chosen from the list the form is
filtered on that value. The default value of the list is "*". I
requery the form on the timer event 100ms after it is opened. If this
isn''t done the values don''t show because the of the way the query uses
a field on the form as one of it''s criteria. The failure that is
occurring makes the form open and not show any records, when it should
be showing them all.

What I''ve found, since my last post is that the database works fine on
an Access 2000 installation that does not have any service packs
installed - I''ve tried this on a clean install on another machine.
The problems appear when the installation of Access 2000 has service
release 1a or later applied. I tried this by installing service pack
1a - problem appeared - uninstalled Access 2000 and reinstalled
without the service pack - problem disappeared. As stated earlier the
database runs fine on Access 2003.

I guess the moral to the story is if you want an Access 2000 database,
write it in Access 2000, not Access 2003, even though the Access 2000
file format is used by default.

If you have any other ideas as to what is causing this bizarre
behaviour, I''d be grateful to hear them.

Regards.

这篇关于计时器事件不会在Access 2000中触发的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！