syntax error at or near "{" at character 86(#-1)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am connected to a SQL database. My queries work fine if I use the default
table join "...where the joined fields from both tables are equal." If I
change the join to "..use all records from one and the records from the
other where they match" I get an "ODBC call failed message,syntax error at or
near "{" at character 86(#-1). "

Ideas?
 
Jim:

The following KB article documents a similar (although not exact) error. If
this does not address your issue, maybe you can post additional details
regarding the query or queries, version of Access, etc.

http://support.microsoft.com/default.aspx?scid=kb;en-us;303257

--
David Lloyd
MCSD .NET
http://LemingtonConsulting.com

This response is supplied "as is" without any representations or warranties.


I am connected to a SQL database. My queries work fine if I use the default
table join "...where the joined fields from both tables are equal." If I
change the join to "..use all records from one and the records from the
other where they match" I get an "ODBC call failed message,syntax error at
or
near "{" at character 86(#-1). "

Ideas?
 
I am in Access 2003. Connecting using the PostgeSQL ODBC driver. I have the
tracking turned on and it shows a different statement SQL statement created
in Access than is being actually sent to SQL.
____________________________________________________________
This is the error message I get when I execute a query with an outer join.

What Access shows in the SQL box:

SELECT
items.item, mfg_vendors.vendor
FROM
items LEFT JOIN mfg_vendors ON items.vendor = mfg_vendors.vendor;


What Access actually sends to the ODBC driver:

SELECT
"items"."item","mfg_vendors"."vendor"
FROM
{oj "items" LEFT OUTER JOIN "mfg_vendors" ON ("items"."vendor" =
"mfg_vendors"."vendor" ) }
________________________________________________________________

Note the "{oj" that was added to the version that was sent to the ODBC.
That seems to be the problem. The Jet driver seems to be in there at about
this point in the communication, but I can't see where any settings would
change this issue.

Any other thoughts?

Thanks

Jim
 
Back
Top