Access 2003 ODBC问题 [英] Access 2003 ODBC Problem

问题描述

我有一个Access 2003 .mde坐在SQL Server上。

的表格应用程序也位于服务器上。我在大约10台机器中的一台机器上遇到了问题。

ODBC。所有其他机器使用我的

Access 2003 .mde看到链接表没有问题。我已经配置了用户DSN（在控制面板，管理工具下）

选项卡以匹配其他机器设置的内容，但这不起作用。

我一直收到ODBC失败的错误消息。是否需要在系统DSN选项卡下列出

？也许是

驱动程序的东西？文件DSN标签在10台机器上有不同的列表，所以

我不知道该怎么办。

I have an Access 2003 .mde sitting on an SQL Server. The tables for
the application also sit on the Server. I''m having a problem with
ODBC on only one of about 10 machines. All the other machines using my
Access 2003 .mde see the linked tables without a problem. I''ve
configured the User DSN (under Control Panel, Administrative Tools)
tab to match what the other machines are set to, but this didn''t work.
I keep getting an error message that ODBC failed. Does anything need
to be listed under the System DSN tab? Maybe something with the
drivers? The File DSN tab has different lists on the 10 machines, so
I''m not sure what to do with this.

推荐答案

如果你有多个用户登录到服务器上的同一个.MDE，那么你b $ b会大大增加该.MDE的破坏概率。微软和其他知识渊博的团队非常强烈推荐的是，你给每个用户提供他们自己的客户副本;如果运行WTS或Citrix来执行服务器上的Access客户端，仍然会在每个文件夹中为每个用户提供他们自己的

副本。这不是你当前问题的答案，但如果你分发前端，你可能会消除_this_问题

（但可能面临一些不同的问题） 。


如果分发和更新客户端应用程序似乎是一项艰巨的任务，MVP Tony

Toews有一个可免费下载的前端更新程序（非常

帮助）网站， http：// www。 granite.ab.ca/accsmstr.htm 。


Larry Linson

Microsoft Access MVP

Dragon ; < XS ******* @ yahoo.com>在留言中写道

新闻：3e ************************ @ posting.google.com ...

If you have multiple users logging in to the same .MDE on the server, you
significantly increase the probability of corruption of that .MDE. The very
strong recommendation of Microsoft and other knowledgeable parties is that
you give each user their own copy of the client; if running WTS or Citrix to
execute the Access clients on the server, still give each user their own
copy in separate folders. That isn''t the answer to your current problem, but
if you distribute the front ends, you will likely eliminate _this_ problem
(but may face some different ones).

If distributing and updating client apps seems a daunting task, MVP Tony
Toews has a Front End Updater that is free for the downloading at his (very
helpful) site, http://www.granite.ab.ca/accsmstr.htm.

Larry Linson
Microsoft Access MVP
"Dragon" <xs*******@yahoo.com> wrote in message
news:3e************************@posting.google.com ...

我有一个Access 2003 .mde坐在SQL Server上。应用程序表也位于服务器上。我在大约10台机器中只有一台机器上出现了问题。使用我的
Access 2003 .mde的所有其他机器看到链接表没有问题。我已经配置了用户DSN（在控制面板，管理工具下）选项卡以匹配其他计算机的设置，但这不起作用。
我一直在ODBC失败的错误消息。是否需要在系统DSN选项卡下列出任何内容？也许是
司机的东西？文件DSN选项卡在10台机器上有不同的列表，所以
我不知道该如何处理。

I have an Access 2003 .mde sitting on an SQL Server. The tables for
the application also sit on the Server. I''m having a problem with
ODBC on only one of about 10 machines. All the other machines using my
Access 2003 .mde see the linked tables without a problem. I''ve
configured the User DSN (under Control Panel, Administrative Tools)
tab to match what the other machines are set to, but this didn''t work.
I keep getting an error message that ODBC failed. Does anything need
to be listed under the System DSN tab? Maybe something with the
drivers? The File DSN tab has different lists on the 10 machines, so
I''m not sure what to do with this.

确保你在每台机器上都有相同的ODBCE驱动程序。


DSN包含连接信息。你可以使用

连接信息存储在mde（一个DSN'无连接），

文件（文件dsn）或某个地方的注册表中。 />

Access使用的实际连接信息将是

当前打开的连接信息的组合，

存储在数据库中的信息，和DSN（如果使用的话）。


如果您尝试在mde使用时添加或更改连接，则只有当前打开的连接

，所以

不重要。


如果用户有不同的DSN，或DSN的内容

不同，那么他们需要拥有自己的副本

MDE。否则连接信息会变得混乱，因为数据库中存储的连接信息将会与不同的DSN信息相混淆。


如果连接信息有任何不同，每个

用户应该拥有自己的MDE副本，可以将其重新连接到
链接使用正确的连接信息。


用户DSN和文件DSN的存储方式不同。每个DSN

包含连接信息。如果您使用的是DSN，那么

肯定需要确定您正在使用的DSN。它是一个

文件DSN吗？还是用户DSN？您不使用的DSN'

不重要。你使用的一个DSN（如果你是使用DSN的
）在所有机器上应该是相同的。即使你使用单独的MDE副本，并在每台PC上重新链接

，你仍然应该确保你没有多个/>
不同的DSN副本，因为这肯定会让你感到困惑

你！


（大卫）

" Dragon" < XS ******* @ yahoo.com>在留言中写道

新闻：3e ************************ @ posting.google.com ...

Make sure that you have the same ODBCE DRIVERs on each machine.

A DSN contains the connection information. You can use
connection information stored in the mde (a DSN''less connection),
in a file (a file dsn) or in the registry somewhere.

The actual connection information used by Access will be a
combination of information from currently open connections,
information stored in the database, and the DSN if one is used.

You will only have currently open connections if you try to
add or change a connection while the mde is in use, so that
shouldn''t matter.

If the users have different DSN''s, or the content of the DSN''s
is different, then they need to have their own copies of the
MDE. Otherwise the connection information will get confused,
because the stored connection information in the database will
get mixed up with the different DSN information.

If the connection information is different in any way, each
user should have their own copy of the MDE, which can be re-
linked to use the correct connection information.

User DSN''s and File DSN''s are stored differently. Each DSN
contains connection information. If you are using a DSN, you
certainly need to work out which DSN you are using. Is it a
file DSN? Or a User DSN? The DSN''s which you are NOT using
don''t matter. The one DSN that you ARE using (if you are
using a DSN) should be identical on all machines. Even if
you are using separate copies of the MDE, and re-linking on
each PC, you still should make sure that you don''t have multiple
different copies of the DSN, because that is sure to confuse
you!

(david)

"Dragon" <xs*******@yahoo.com> wrote in message
news:3e************************@posting.google.com ...

我有一个Access 2003 .mde坐在SQL Server上。应用程序表也位于服务器上。我在大约10台机器中只有一台机器上出现了问题。使用我的
Access 2003 .mde的所有其他机器看到链接表没有问题。我已经配置了用户DSN（在控制面板，管理工具下）选项卡以匹配其他计算机的设置，但这不起作用。
我一直在ODBC失败的错误消息。是否需要在系统DSN选项卡下列出任何内容？也许是
司机的东西？文件DSN选项卡在10台机器上有不同的列表，所以
我不知道该怎么做。

I have an Access 2003 .mde sitting on an SQL Server. The tables for
the application also sit on the Server. I''m having a problem with
ODBC on only one of about 10 machines. All the other machines using my
Access 2003 .mde see the linked tables without a problem. I''ve
configured the User DSN (under Control Panel, Administrative Tools)
tab to match what the other machines are set to, but this didn''t work.
I keep getting an error message that ODBC failed. Does anything need
to be listed under the System DSN tab? Maybe something with the
drivers? The File DSN tab has different lists on the 10 machines, so
I''m not sure what to do with this.

" Sherwood Wang <嘘**** @ waynesworld.net>写了

"Sherwood Wang" <Sh****@waynesworld.net> wrote

* Sherwood Wang MVP *
（也是sys eng，bs，ms）

*Sherwood Wang MVP*
(is also sys eng, bs, ms)

（是常驻巨魔XMVP的sockpuppet。不是微软MVP。是b
bs的来源。）

(is sockpuppet of resident troll XMVP. is not Microsoft MVP. is source of
much bs.)

这篇关于Access 2003 ODBC问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！