在Access 2000到2003之后，调用VBA过程的升级事件处理程序不起作用 [英] After Access 2000 to 2003 upgrade event handlers that call VBA procedures don't work
问题描述
我多年来一直使用我的Access 2000数据库来运行手术等待名单。它位于共享驱动器上，可以通过XP下运行Access 2000和2003混合的多台计算机访问。
2000台计算机中的一台升级到2003年，并且wham - ;升级到访问2003后，调用VBA过程的事件处理程序不起作用 （引自http://office.microsoft.com/en-us/access/HA011225981033.aspx#030）。这种情况现在发生在所有机器上，包括那些在升级这台机器之前在2003年正常运行的机器。
Microsoft KB建议如果在没有更新到沙箱的情况下启用Sandbox，则会出现这种问题。 Jet的最新版本，但更新的机器（据我所知，所有其他机器）都有最新的Jet。降低Access中的宏安全级别和注册表项中的沙箱安全级别没有帮助。
感谢收到的任何建议。
多年来我一直在使用我的Access 2000数据库运行手术等待名单。它位于共享驱动器上，可以通过XP下运行Access 2000和2003混合的多台计算机访问。
2000台计算机中的一台升级到2003年，并且wham - ;升级到访问2003后，调用VBA过程的事件处理程序不起作用 （引自http://office.microsoft.com/en-us/access/HA011225981033.aspx#030）。现在所有机器上都会发生这种情况，包括那些在升级这台机器之前在2003年正常运行的机器。
Microsoft KB建议如果在没有更新到沙箱的情况下启用Sandbox，则会出现这种问题。 Jet的最新版本，但更新的机器（据我所知，所有其他机器）都有最新的Jet。降低Access中的宏安全级别和注册表项中的沙箱安全级别没有帮助。
任何建议都感激不尽。
ENTBedford，
您提供的链接提到了其他几个步骤，您没有提及，例如：
1.查看不安全的表达式列表并修复您使用的表格
2.在重新编译代码后更新自签名证书
如果您没有这样做，我认为您需要返回并按照您提供的链接一步一步。
感谢Puppydog。
我检查过不安全的表达式 - 没有。它是在代码运行之前触发错误的实际事件。
您能否在重新编译之后解释有关自我认证的更多信息 - 这对我来说是全新的。
谢谢Puppydog。
我检查过不安全的表达式 - 没有。这是在代码运行之前触发错误的实际事件。
您能否在重新编译之后解释有关自我认证的更多信息 - 这对我来说是全新的。
ENTBedford，
我不知道数字签名是否是您问题的答案，但值得研究。有关数字签名的完整说明，请参阅此链接。
http://office.microsoft.com/en-us/ac...397921033.aspx
让我知道这是否有帮助
Ive been using my Access 2000 database for years to run a surgical waiting list. It''s on a shared drive and is accessed by several machines running a mixture of Access 2000 and 2003 under XP.
One of the 2000 machines was upgraded to 2003 and wham - "Event handlers that call VBA procedures don''t function after upgrade to access 2003" (quote from http://office.microsoft.com/en-us/access/HA011225981033.aspx#030). This happens on ALL machines now, including those that were working fine with 2003 before this one machine was upgraded.
Microsoft KB suggests this happens as a Sandbox problem if Sandbox is enabled without updateing to the latest version of Jet, but the updated machine (and all others as far as I know) has the latest Jet. Reducing macro security level in Access and sandbox security level in registry key hasn''t helped.
Any suggestions gratefully recieved.
Ive been using my Access 2000 database for years to run a surgical waiting list. It''s on a shared drive and is accessed by several machines running a mixture of Access 2000 and 2003 under XP.
One of the 2000 machines was upgraded to 2003 and wham - "Event handlers that call VBA procedures don''t function after upgrade to access 2003" (quote from http://office.microsoft.com/en-us/access/HA011225981033.aspx#030). This happens on ALL machines now, including those that were working fine with 2003 before this one machine was upgraded.
Microsoft KB suggests this happens as a Sandbox problem if Sandbox is enabled without updateing to the latest version of Jet, but the updated machine (and all others as far as I know) has the latest Jet. Reducing macro security level in Access and sandbox security level in registry key hasn''t helped.
Any suggestions gratefully recieved.ENTBedford,
The link you provided mentions several other steps to take, none of which you mention doing, such as:
1. reviewing the unsafe expressions list and fixing the ones you use
2. updating your self signed certficate after your code was recompiled
If you did not do the above, I think you need go back and follow the link you provided step by step.
Thanks Puppydog.
I have checked for unsafe expressions - there are none. it''s the actual event that triggers the error before the code runs.
Can you explain more about self certifying after recompiling please - that''s all new to me.
Thanks Puppydog.
I have checked for unsafe expressions - there are none. it''s the actual event that triggers the error before the code runs.
Can you explain more about self certifying after recompiling please - that''s all new to me.
ENTBedford,
I don''t know if the digital signature is the answer to your problem, but it is worth looking into. See this link for a full explanation of digital signatures.
http://office.microsoft.com/en-us/ac...397921033.aspx
Let me know whether this helped or not.
这篇关于在Access 2000到2003之后，调用VBA过程的升级事件处理程序不起作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
