Access表如何在启动时链接 [英] How does Access table link at startup

查看:83
本文介绍了Access表如何在启动时链接的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个复杂的链接问题。在我了解详细信息之前,

我想知道Access在启动时如何链接到后端文件,之后我已经分配了我的应用程序
给客户。


这就是问题所在。当我正在处理我的应用程序时,我与我的计算机上的后端相关联。当我分发应用程序时,后端文件显然位于

不同的位置(在客户端服务器上)。


但是我的应用程序第一次启动时在客户端位置,后端的

连接字符串仍然是我的开发计算机

,这些字符串显然无效。


现在我有一个自定义链接例程并使用启动器。启动器通过Command传递

到我的应用程序,后端文件的正确位置。在过去的6个月里,这已经完美无缺地工作了,但是最近对客户的更新

无法正常工作并产生链接错误。但是,我遇到了麻烦

复制问题。


所以,现在,我只想知道Access遇到什么时会做什么

我提到的情况。仅当代码或某些操作

尝试从无效的表链接中提取数据时才会生成错误。换句话说,

Access将允许启动时无效的连接字符串,并且仅在采取某些操作实际查看或选择来自

>
链表。我应该提一下,我也使用RWOP查询,所以我想知道为什么在

RWOP查询时启动时没有产生错误的原因从链接表中选择数据。我想这肯定意味着

它实际上并没有选择直到某种类型的动作被采取(即

用户打开RWOP查询或代码尝试执行关于查询的动作)。


了解这是如何工作的,我认为这将有助于我解决我的问题。


谢谢。


-

通过 http发布的消息://www.accessmonster.com

I''m having a complicated linking problem. Before I get into the particulars,
I''d like to know how Access links to the back-end file at startup, AFTER I''ve
distributed my application to the client.

Here''s the issue. While I''m working on my app, I''m linked to the backend on
my computer. When I distribute the app, the backend file is obviously in a
different location (on the client server).

But the first time my app is started up at the client location, the
connection strings for the backend will still be to my development computer
and these strings are obviously invalid.

Now I have a custom linking routine and use a launcher. The launcher passes
to my app via Command, the correct location of the backend files. This has
worked flawlessly over the past 6 months, but a recent update to the client
failed to work and generated a linking error. But, I''m having trouble
replicating the problem.

So, for now, I would just like to know what Access does when it encounters
the situation I mentioned. Is an error generated only if code or some action
attempts to extract data from a table link that is not valid. In other words,
Access will allow the invalid connection strings on startup and an error is
only generated when some action is taken to actually view or select data from
the linked table. I should mention that I use RWOP queries as well, so I
guess I''m wondering why there isn''t an error generated at startup when the
RWOP query selects data from the linked table. I guess this must mean that
it doesn''t actually select until an action of some type is taken (i.e. the
user opens the RWOP query or code tries to perform an action on the query).

Understanding how this works, I think will help me in solving my problem.

Thanks.

--
Message posted via http://www.accessmonster.com

推荐答案

>换句话说,Access将允许无效的连接字符串在
>In other words, Access will allow the invalid connection strings on

>启动时,只有在采取某些操作实际查看或从链接表中选择数据时才会生成错误。
>startup and an error is only generated when some action is taken to
actually view or select data from the linked table.



是的。访问不会注意到表链接无效,直到它尝试实际使用它为
。然后你得到运行时错误3044

(...不是一个有效的路径)


rdemyan通过AccessMonster.com写道:

Yes. Access does not notice that a table link is invalid until it tries
to actually use it for something. Then you get run-time error 3044
("... is not a valid path)

rdemyan via AccessMonster.com wrote:


我有一个复杂的链接问题。在我了解详细信息之前,

我想知道Access在启动时如何链接到后端文件,之后我已经分配了我的应用程序
给客户。


这就是问题所在。当我正在处理我的应用程序时,我与我的计算机上的后端相关联。当我分发应用程序时,后端文件显然位于

不同的位置(在客户端服务器上)。


但是我的应用程序第一次启动时在客户端位置,后端的

连接字符串仍然是我的开发计算机

,这些字符串显然无效。


现在我有一个自定义链接例程并使用启动器。启动器通过Command传递

到我的应用程序,后端文件的正确位置。在过去的6个月里,这已经完美无缺地工作了,但是最近对客户的更新

无法正常工作并产生链接错误。但是,我遇到了麻烦

复制问题。


所以,现在,我只想知道Access遇到什么时会做什么

我提到的情况。仅当代码或某些操作

尝试从无效的表链接中提取数据时才会生成错误。换句话说,

Access将允许启动时无效的连接字符串,并且仅在采取某些操作实际查看或选择来自

>
链表。我应该提一下,我也使用RWOP查询,所以我想知道为什么在

RWOP查询时启动时没有产生错误的原因从链接表中选择数据。我想这肯定意味着

它实际上并没有选择直到某种类型的动作被采取(即

用户打开RWOP查询或代码尝试执行关于查询的动作)。


了解这是如何工作的,我认为这将有助于我解决我的问题。


谢谢。


-

通过 http发布的消息://www.accessmonster.com


我一直在各种条件下测试我的代码。移动文件夹

后端文件位于。只移动

文件夹中的后端文件。更改有效后端文件夹中后端文件的名称。

在每种情况下,都会调用我的自定义错误消息并显示我的自定义链接

屏幕。我还没有得到运行时错误3044

出现。当客户通过电话告诉我他得到了这个

错误时,我感到很困惑,现在更加困惑,因为我只是看不出怎样

这可能发生。


现在当我的应用程序启动时,它会在启动期间删除所有链接的表格

并根据从中传入的位置信息重新创建它们

启动器。因此,应用程序会在启动之前删除链接,然后才能在链接上执行任何类型的操作(打开或代码操作),我不知道这是怎么回事

假设我的启动代码如何工作,甚至可以生成错误。


此外,我的客户端出现的错误发生在

启动时调用的模块中常规。在我的客户的情况下,如果在链接期间出现问题

那时应该生成错误,而不是在后续模块中生成错误。


Gord写道:
I''ve been testing my code under a variety of conditions. Moving the folder
the back-end files are located in. Moving just the back-end files out of the
folder. Changing the name of the back-end files in a valid back-end folder.
In every case, my custom error messages are invoked and my custom linking
screen gets displayed. I have not yet been able to get run-time error 3044
to appear. When the client told me over the phone that he was getting this
error, I was puzzled and am now even more puzzled, since I just don''t see how
this could happen.

Right now when my app launches, it deletes all linked tables during startup
and recreates them based on the location information passed in from the
launcher. So given that the app deletes the links at startup before any type
of action is done on the links (opening or code action), I don''t see how this
error can even be generated given how my startup code works.

Also the error that my client got occurred in a module that is invoked in the
startup routine. In my client''s case, if there was a problem during linking
an error should have been generated at that time, not in a subsequent module.

Gord wrote:

>>换句话说,Access将允许
启动时无效的连接字符串和只有在采取某些操作实际查看或从链接表中选择数据时才会生成错误。
>>In other words, Access will allow the invalid connection strings on
startup and an error is only generated when some action is taken to
actually view or select data from the linked table.


是的。 Access尝试
实际使用它时,不会注意到表链接无效。然后你得到运行时错误3044
(...不是一个有效的路径)


Yes. Access does not notice that a table link is invalid until it tries
to actually use it for something. Then you get run-time error 3044
("... is not a valid path)


>我有一个复杂的链接问题。在我了解详细信息之前,
我想知道Access在启动后如何链接到后端文件,我已经b $ b
>I''m having a complicated linking problem. Before I get into the particulars,
I''d like to know how Access links to the back-end file at startup, AFTER I''ve


[引用文本剪辑 - 28行]

[quoted text clipped - 28 lines]


>>
谢谢。
>>
Thanks.



-

通过AccessMonster.com发布消息
http://www.accessmonster.com/Uwe/For...ccess/ 200609/1

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200609/1


我希望这个论坛能够编辑帖子。


To很明显,在我的代码重新创建

链接后,客户端发生了错误。此外,3044错误列出的文件名确实存在于服务器上的
。我唯一能想到的是服务器上出现了某种打击问题。但我让他登录至少6到8次来测试一些东西,并且每次都在同一个模块中发生错误。所以基于

,很难相信这可能是服务器打嗝。


rdemyan写道:
I wish this forum had the ability to edit posts.

To be clear, the error the client got occurred after my code recreated the
links. Also, the file name listed by the 3044 error does in fact exist out
on the server. The only thing I can think of is that there was some kind of
hiccup at the server. But I had him logon at least 6 to 8 times to test a
few things and the error occurred each time in the same module. So based on
that, it is hard to believe that this could be a server hiccup.

rdemyan wrote:

>我一直在各种条件下测试我的代码。移动文件夹
后端文件位于。只将后端文件移出
文件夹。更改有效后端文件夹中后端文件的名称。
在每种情况下,都会调用我的自定义错误消息并显示我的自定义链接
屏幕。我还没有得到运行时错误3044
出现。当客户通过电话告诉我他得到了这个错误时,我感到困惑,现在更加困惑,因为我只是看不出这是怎么发生的。

现在,当我的应用程序启动时,它会在启动期间删除所有链接的表格,并根据从
启动程序传入的位置信息重新创建它们。因此,在应用程序在链接上执行任何类型的操作(打开或代码操作)之前,应用程序会在启动时删除链接,我不知道如何生成这个
错误,因为如何我的启动代码有效。

我的客户端发生的错误也发生在
启动例程中调用的模块中。在我的客户端的情况下,如果链接期间出现问题,那么当时应该生成错误,而不是后续模块。
>I''ve been testing my code under a variety of conditions. Moving the folder
the back-end files are located in. Moving just the back-end files out of the
folder. Changing the name of the back-end files in a valid back-end folder.
In every case, my custom error messages are invoked and my custom linking
screen gets displayed. I have not yet been able to get run-time error 3044
to appear. When the client told me over the phone that he was getting this
error, I was puzzled and am now even more puzzled, since I just don''t see how
this could happen.

Right now when my app launches, it deletes all linked tables during startup
and recreates them based on the location information passed in from the
launcher. So given that the app deletes the links at startup before any type
of action is done on the links (opening or code action), I don''t see how this
error can even be generated given how my startup code works.

Also the error that my client got occurred in a module that is invoked in the
startup routine. In my client''s case, if there was a problem during linking
an error should have been generated at that time, not in a subsequent module.

>>>换句话说,Access将允许启动时无效的连接字符串,并且只有在对
采取某些操作时才会生成错误
>>>In other words, Access will allow the invalid connection strings on
startup and an error is only generated when some action is taken to


[引用文字剪辑 - 9行]

[quoted text clipped - 9 lines]


>>>
感谢。
>>>
Thanks.



-

通过AccessMonster.com发布消息
http://www.accessmonster.com/Uwe/For。 ..ccess / 200609/1

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200609/1


这篇关于Access表如何在启动时链接的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆