Solved

"ODBC call failed" on one specific query to SQL Server, no matter ODBC, ADO, pass through, etc.

Posted on 2011-02-10
5
233 Views
Last Modified: 2012-05-11
The same query can work using one variable in the where clause, but fail using another -- same table, same query.
0
Comment
Question by:cagilbert
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 34868095
Post the query and the consition that it fails with and the one that is successful.
0
 

Author Comment

by:cagilbert
ID: 34868205
set rs = db.OpenRecordset("Select * from tbl where TSid = " & lngTsID)

is one variation that fails.  lngTSIS is a number.  sometimes it works sometimes not.
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 34876323
I am sorry but I am afraid that does not help me.  I was asking for the specific values in your condition that fail and which are successful.

Hopefully, someone will step up to the plate with some insight.

Good luck.
0
 

Accepted Solution

by:
cagilbert earned 0 total points
ID: 34876498
I now have a work-around that copies the records from the one SQL Server table that is causing a problem to the Access front-end,  Then I've changed the query to use that data.  (The previous batch is deleted each time and the front-end compacts each night so it shouldn't get too much bigger.)  
0
 

Author Closing Comment

by:cagilbert
ID: 34904897
It doesn't figure out the issue, but it solves the problem.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Audit has been really one of the more interesting, most useful, yet difficult to maintain topics in the history of SQL Server. In earlier versions of SQL people had very few options for auditing in SQL Server. It typically meant using SQL Trace …
Long way back, we had to take help from third party tools in order to encrypt and decrypt data.  Gradually Microsoft understood the need for this feature and started to implement it by building functionality into SQL Server. Finally, with SQL 2008, …
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question