We are attempting to load data into DBISAM using SQL Server Integration Services (SSIS) 2008.  The software using the DBISAM database is called TotalMD and they are using version 4.1 of the Engine according to the Server Administration Utility.  The ODBC driver we are using on the SQL Server box is 4.35.00.01.  Also, our SQL Server has all the latest patches and service packs as of February 2013.

We are noticing this error on various fields in a SSIS sequence that worked fine previously.  By removing the offending fields, we can get the package to run fine, however, we obviously need those fields.  One of the fields is an Integer datatype in DBISAM's database.  Even if we populate this field to a default of 0 rather than NULL (we would need NULL), we would get this error.  And that field is just one example.

Any help is appreciated.  Thank you all in advanced for your consideration.

Here is the error from SSIS:


[ADO NET Destination [4367]] Error: An exception has occurred during data insertion, the message returned from the provider is: ERROR [42000] [Elevate Software][DBISAM] DBISAM Engine Error # 11949 SQL parsing error - Expected NULL, Boolean, SmallInt, Word, AutoInc, Integer, LargeInt, Currency, Float, or BCD expression but instead found ? in INSERT SQL statement at line 1, column 754

The trace file from ODBC is attached to this post.

JamesNT

James,

<< We are noticing this error on various fields in a SSIS sequence that
worked fine previously.  By removing the offending fields, we can get the
package to run fine, however, we obviously need those fields.  One of the
fields is an Integer datatype in DBISAM's database.  Even if we populate
this field to a default of 0 rather than NULL (we would need NULL), we would
get this error.  And that field is just one example. >>

That error indicates that one of the parameters that was specified in the
parameterized SQL statement was not assigned a value prior to the SQL being
executed.  When this happens, DBISAM has no idea what type the parameter
should be, so it has to issue an error.  More specifically, this indicates
that the client application didn't call the SQLBindParameter API call to
bind a parameter buffer to the parameter that is causing the error
("Relation to Subscriber 2" field).

BTW, please email support@elevatesoft.com and start a support session for
issues like this.  They are customer-specific issues, and not general
questions of interest to all customers, so they need to be handled in that
fashion.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com