Re: ODBC call failed - weird behavior
From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 03/11/04
- Next message: Lee Scheffler: "Multiple statement handles on one connection"
- Previous message: Rachel Gibson: "connecting on SQL server database to another SQL server database"
- In reply to: Ragnar Midtskogen: "ODBC call failed - weird behavior"
- Next in thread: Ragnar Midtskogen: "Re: ODBC call failed - weird behavior"
- Reply: Ragnar Midtskogen: "Re: ODBC call failed - weird behavior"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 11 Mar 2004 08:16:58 -0700
It could be an MDAC issue. You could run the MDAC component
checker on a machine where the app works and another machine
where the app gets the ODBC error and see if there are any
differences in MDAC versions. You can get component checker
from:
http://msdn.microsoft.com/data/downloads/tools/default.aspx
You could also turn on ODBC tracing then reproduce your
error and then turn tracing off again. You could open up the
ODBC trace log, look for specifics of what's failing and try
to track down the issue from there.
-Sue
On Wed, 10 Mar 2004 19:05:29 -0500, "Ragnar Midtskogen"
<ragnar_ng@optonline.net> wrote:
>Hello,
>
>I have been working on updating an Access 2000 application that uses linked
>ODBC tables to connect to an SQL Server 2000. My development machine is
>connected to the server over a Microsoft LAN, at 100Mbits.
>Both the Office 2000 on my development machine and the SQL server has all
>the latest SP's
>Everything worked fine for months until today. I am not aware of any changes
>to ether machine since yesterday.
>Now, there is one table that can not be opened any more.
>I can access all the other tables ecxept that one. When I try to open it I
>get the message "ODBC call failed". The table is displayed but with #Name?
>in all columns for all records.
>Once that has happened I get the same message for all tables. In addition to
>"ODBC call failed" there is also
>"[Microsoft][ODBC SQL Server Driver][Communication link failure (#0)".
>When I close down and reopen the app I can again access all tables except
>the bad one.
>At first, I thought the table had gotten corrupted, but I can open the table
>just fine on the server. If I set up an ODBC on the server with the same
>name I and run my application there. the problem table opens fine.
>I removed the ODBC and set it up again with the same properties, client uses
>TCP/IP network library, and I am using SQL Server authentication.
>I am using MDAC 2.6 SP2, and I did a refresh, but it did not solve problem.
>I ran
>I am wondering if I should update to 2.8
>
>If anyone has a suggestion I would appreciate it very much.
>
>Ragnar
>
- Next message: Lee Scheffler: "Multiple statement handles on one connection"
- Previous message: Rachel Gibson: "connecting on SQL server database to another SQL server database"
- In reply to: Ragnar Midtskogen: "ODBC call failed - weird behavior"
- Next in thread: Ragnar Midtskogen: "Re: ODBC call failed - weird behavior"
- Reply: Ragnar Midtskogen: "Re: ODBC call failed - weird behavior"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
