Feedback

Feedback

Did this article resolve your question/issue?

   

Article

Error: "ODBC Call Failed" When encountering datatype mismatch with ODBC Salesforce Driver

Printable View

Information

 
TitleError: "ODBC Call Failed" When encountering datatype mismatch with ODBC Salesforce Driver
URL Nameerror-odbc-call-failed-when-encountering-datatype-mismatch-with-odbc-salesforce-driver
Article Number000159364
EnvironmentProduct: Connect for ODBC Salesforce Driver
Version: 7.1
O/S: Windows
Database: Salesforce
Application: Microsoft Access
Question/Problem Description
While using a linked table to a table object on Salesforce, an error occurs when the linked column is defined as SQL_BIT while the data in the column contains string data.
Steps to Reproduce
Clarifying Information
Error MessageODBC Call failed

[DataDirect[ODBC Salesforce Driver] Invalid character value in column 133
Defect Number
Enhancement Number
Cause
The underlying problem was that there were two versions of the column.  The driver, by default, is stripping the custom suffix "__c" from the column name.  Apparently there was a second definition of the column and could have coincided with the name of the column causing Access to detect on version of the column while the driver perceived a different definition of the column.
Resolution
Changing the "CustomSuffix" option of the "ConfigOptions" configuration to a value of "Include" allowed the correct version of the column (including the __c suffix) to be detected and linked to by MS Access.

Ensure that there are no conflicting column names or column definitions in the table.
Workaround
Notes
Last Modified Date7/12/2019 11:22 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.


Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use Privacy Center Security Center Trademarks License Agreements Code of Conduct Careers Offices
Do Not Sell My Personal Information