Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 395
  • Last Modified:

ODBC Call Failed

I have an access app that connects to sql server via odbc, on 2 of my computers it works fine but the same code on 2 other computer give me greif I have attached 2 log files one from each computer, any ideas
SQLerr.txt
SQLworking.txt
0
jroulgnd
Asked:
jroulgnd
1 Solution
 
Brendt HessSenior DBACommented:
The issue appears to be a difference in how the two access connections handle the QUOTED_IDENTIFIER state.  By default, SQL Server does not allow quotation marks to be used around SQL identifiers, as you have in the code:

SELECT "dbo"."PS10100"."dDOCSUFFIX" ,"dbo"."PS10100"."dAPPDATE" ,"dbo"."PS10100"."dISSUEDDATE" .....

You have three options:
1)  Replace the quotation marks with square brackets, e.g.:

SELECT [dbo].[PS10100].[dDOCSUFFIX] ,[dbo].[PS10100].[dAPPDATE] ,[dbo].[PS10100].[dISSUEDDATE] ....

2)  Set the QUOTED_IDENTIFIER parameter ON in your connection

3)  Set the QUOTED_IDENTIFIER option ON in your database using ALTER DATABASE, e.g.

ALTER DATABASE MyDB SET QUOTED_IDENTIFIER ON
0
 
GRayLCommented:
grief!
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now