UCase无法在A97运行时安装中运行... [英] UCase not working in A97 runtime installation...

问题描述

已经安装了4个月的运行时间。升级

今天新版本0.07起0.06。在发布时，报告错误...


错误初始化，模块AutoExec，函数不可用于

查询表达式...''UCase（[ SerialNum]）


这个表达式已经在应用程序的所有版本中运行了4个月。

我今天没有触及运行时可执行文件。我只是将一个新的mde复制到app dir上。发生了两次此错误（我是远程启动，而不是坐在控制台上）。怀疑？

解决方案

如果任一台机器上任何引用的库的版本发生了变化，

有时会在一台机器上创建数据库机器不会在另一个上工作。通常，你可以通过在发生故障的机器上安装Windows更新来解决这个问题，或者通过在故障机器上删除并重新创建引用来解决这个问题，然后再使用它。

作为新的主副本。


超过一半的时间发生这种情况，如果你在

故障机器上打开VB编辑器，并且转到工具 - >引用，其中一个会说MISSING。

您需要删除该引用，关闭引用窗口，重新打开

窗口，然后重新添加已删除的引用。


所有这一切的一个非常违反直觉的方面是，如果-any-引用

被破坏，那么参考文件就无效了。


星期三，2005年9月14日02:01:22 -0400，MLH< CR ** @ NorthState.net>写道：

已运行4个月的运行时安装。升级
今天新版本0.07起0.06。在发布时，错误报告...

错误初始化，模块AutoExec，函数在
查询表达式中不可用...''UCase（[SerialNum]）
<这个表达已经在应用程序的所有版本中使用了4个月。
我今天没有触及运行时可执行文件。我只是将一个新的mde复制到app dir。两次启动此错误（我远程启动，而不是坐在控制台）。怀疑？

Thx，Steve。我将不得不去客户的业务，安装Access

并打开VB编辑器，给你的理论一个测试。昨晚，我远程登录了
，将最新的早期app rev（0.06）

复制回app dir并启动 - 问题不会发生

运行时。我想不出我在构建

rev 0.07时添加的任何内容导致包含额外的引用，

但你永远不知道。我在这里的0.07开发副本中遇到了一些超级奇怪的问题 - 这是肯定的。在我最近的帖子中看看

，标题为......


A97每次打开特定报告时都会关闭


....你会看到我的意思。

如果任一机器上任何引用的库的版本发生了变化，<有时在一台机器上创建的数据库不会在另一台机器上运行。
那真是太糟糕了，对吧？用户可以在没有意识到这可能导致他们的机器上的其他东西无法工作的情况下发生这种情况（IE，我的

app！％

*&安培;！）。根据您的经验，这是否常见？

通常，您可以通过在故障机器上安装Windows更新或通过删除并重新创建失败的参考来解决此问题机器，然后使用那个
作为新的主副本。

超过一半的时间发生这种情况，如果你在
故障机器上打开VB编辑器，然后转到工具 - >引用，其中一个会说MISSING。
您需要删除该引用，关闭引用窗口，重新打开
窗口，然后重新添加已删除的引用。
所有这一切的一个非常违反直觉的方面是，如果-any-参考
被破坏，那么参考文献就没有了。

2005年9月14日星期三02:01:22 -0400，MLH< CR ** @ NorthState.net>写道：

已运行4个月的运行时安装。升级
今天新版本0.07起0.06。在发布时，错误报告...

错误初始化，模块AutoExec，函数在
查询表达式中不可用...''UCase（[SerialNum]）
<这个表达已经在应用程序的所有版本中使用了4个月。
我今天没有触及运行时可执行文件。我只是将一个新的mde复制到app dir。两次启动此错误（我远程启动，而不是坐在控制台）。怀疑？

Have had a runtime installation up for 4 months. Upgraded
today with new ver 0.07 from 0.06. On launch, error reported...

Err in fn Initialize, module AutoExec, function isnt available in
query expression ... ''UCase([SerialNum])

This expression has been in all rev''s of the app for 4 months.
I did not touch the runtime executable today. I merely copied
a new mde to the app dir. Got this error launching twice (am
launching remotely, not sitting at the console). Suspicions?

解决方案

If the version of any referenced library on either machine has changed,
sometimes a database created on one machine won''t work on the other. Usually,
you can fix this by installing windows updates on the failing machine or by
removing and recreating the reference on the failing machine, then using that
as the new master copy.

More than half the time when this happens, if you open the VB Editor on the
failing machine, and go to Tools -> References, one of them will say MISSING.
You need to remove that reference, close the References window, reopen the
window, and re-add the reference that was removed.

One really counterintuitive aspect to all of this is that if -any- reference
is broken, -none- of the references work.

On Wed, 14 Sep 2005 02:01:22 -0400, MLH <CR**@NorthState.net> wrote:

Have had a runtime installation up for 4 months. Upgraded
today with new ver 0.07 from 0.06. On launch, error reported...

Err in fn Initialize, module AutoExec, function isnt available in
query expression ... ''UCase([SerialNum])

This expression has been in all rev''s of the app for 4 months.
I did not touch the runtime executable today. I merely copied
a new mde to the app dir. Got this error launching twice (am
launching remotely, not sitting at the console). Suspicions?

Thx, Steve. I''ll have to go to the client''s business, install Access
and open the VB Editor, giving your theory a test. Last night, I
remotely logged in, copied the most recent earlier app rev (0.06)
back into the app dir and launched - the problem does NOT occur
when it is run. I cannot think of anything I added during build of
rev 0.07 that resulted in the inclusion of an additional reference,
but you never know. I have been having some super strange
problems in my dev copy of 0.07 here - that''s for sure. Have a look
at my recent post entitled...

"A97 closes down each time I open a particular report"

....and you''ll see what I mean.

If the version of any referenced library on either machine has changed,
sometimes a database created on one machine won''t work on the other. That''s a bummer, huh? Users can cause this to happen without realizing
that it may cause something else on their machine not to work (IE, my
app!%

*&!!!). In your experience, is this a common occurrence?
Usually,
you can fix this by installing windows updates on the failing machine or by
removing and recreating the reference on the failing machine, then using that
as the new master copy.

More than half the time when this happens, if you open the VB Editor on the
failing machine, and go to Tools -> References, one of them will say MISSING.
You need to remove that reference, close the References window, reopen the
window, and re-add the reference that was removed.

One really counterintuitive aspect to all of this is that if -any- reference
is broken, -none- of the references work.

On Wed, 14 Sep 2005 02:01:22 -0400, MLH <CR**@NorthState.net> wrote:

Have had a runtime installation up for 4 months. Upgraded
today with new ver 0.07 from 0.06. On launch, error reported...

Err in fn Initialize, module AutoExec, function isnt available in
query expression ... ''UCase([SerialNum])

This expression has been in all rev''s of the app for 4 months.
I did not touch the runtime executable today. I merely copied
a new mde to the app dir. Got this error launching twice (am
launching remotely, not sitting at the console). Suspicions?

这篇关于UCase无法在A97运行时安装中运行...的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！