Feedback
Did this article resolve your question/issue?

   

Article

Error when inserting character data in date column with ODBC driver and bulk load enabled.

Information

 
TitleError when inserting character data in date column with ODBC driver and bulk load enabled.
URL Nameerror-when-inserting-character-data-in-date-column-with-odbc-driver-and-bulk-load-enabled
Article Number000182264
EnvironmentProduct : Connect for SQLServer Wire Protocol driver
Version : All supported versions
Database : SQLServer
OS : All supported platforms
Application : All supported applications
Question/Problem Description
When binding character data for a date column, below errors are returned when EnableBulkLoad is enabled.
Steps to Reproduce-Connect to SQLServer using ODBCTest for Unicode
-SQLExecDirect : create table my_date (col1 date)
-SQLPrepare : insert into my_date values (?)
-SQLSetStmtAttr : SQL_ATTR_PARAMSET_SIZE=22 (3.0) with Value 2
-SQLBindParameter :
ValueType : SQL_C_WCHAR
ParameterType : SQL_WVARCHAR
ParameterValuePtr : 20160101
Columnsize : 20
Bufferlength : 22
-SQLExecute
Clarifying Information
Error Message[DataDirect][ODBC SQL Server Wire Protocol driver]Invalid character value. Error in parameter 1.
[DataDirect][ODBC SQL Server Wire Protocol driver]Operation cancelled. Error in parameter 1.
Defect NumberDefect 61907
Enhancement Number
Cause
The reason an error is seen when using the ‘yyyymmdd’ date format with parameter arrays with bulk and success without bulk is due to a documented limitation of the bulk API that the driver uses. The ODBC spec mentions that the standard ODBC format is required when using the SQL Server bulk API.

When the bulk API is not being used, the driver is able to send the ‘yyyymmdd’ formatted data directly to the server where it is then implicitly converted to the default ‘yyyy-mm-dd’ TSQL default date format.

 
Resolution
Modify code to send ODBC formatted date values to the driver when using bulk load.
Workaround
Disable EnableBulkLoad.
Notes
Last Modified Date2/2/2017 10:02 AM
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.