Advertisement

08.15.2007 at 08:41AM PDT, ID: 22764496
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
7.6

MS Access query runs ok, report shows error: ODBC--Call Failed

Asked by TheUndecider in Microsoft Access Database, MS SQL Server, Access Reports

Tags: , , , ,

Hi, I have a MS Access 2000 database as my front end with a SQL Server 2000 database as my back end.  All the access tables are linked to the ones in the SQL database.

My problem is that I have a set of reports that months ago, they were printing fine.  However, now when I try to run them, I get a "ODBC--Call Failed" error.  This error has only the exclamation icon, a help and a OK button.  It doesn't give me any error number or any other message, just the line mentioned above.

The weirdest part is that when I run the Access query that acts as these report record source it runs fine and fast.  

The query selects a customer from my customers table and some orders from the orders table.  I have a 1 to many relationship between these 2 tables.  After I select the fields I need, I group them by first of customerID to get only 1 record.  The query does show that record when I run it.  The report gets stopped by the odbc error.

I've tried to change the ODBC timeout (currently is at 60) from 0 to 90 with no results.

I have temporarily deleted everything from one of these reports (except its data source) and the error  still shows up.

I've also used the link table manager and updated the mentioned tables in case they were different than the SQL ones and did not help.

What I don't understand is why the query runs perfectly if I run it by itself, but when I ran the report it shows the error.


Any help would be appreciated it.Start Free Trial
 
Keywords: MS Access query runs ok, report sho…
Title
1 ODBC Query Timeout Change
2 What are the options for seeing what k…
3 odbc refresh linked tables
4 Problem using ODBC SQLPrepare, SQ…
5 ODBC
6 ODBC Timing Out
 
Loading Advertisement...
 
[+][-]08.15.2007 at 09:40AM PDT, ID: 19701308

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Microsoft Access Database, MS SQL Server, Access Reports
Tags: access, call, failed, odbc, query
Sign Up Now!
Solution Provided By: InnovativeLogic
Participating Experts: 2
Solution Grade: B
 
 
[+][-]08.15.2007 at 11:40AM PDT, ID: 19702501

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 7-day free trial to view this Assisted Solution or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628