# MySql Ansi ODBC driver fails under certain conditions

**URL:** https://community.linx.software/community/t/mysql-ansi-odbc-driver-fails-under-certain-conditions/183
**Category:** Support
**Created:** [September 11, 2017, 7:16am UTC](https://community.linx.software/community/t/mysql-ansi-odbc-driver-fails-under-certain-conditions/183 "2017-09-11T07:16:47Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![gawie](https://community.linx.software/community/user_avatar/community.linx.software/gawie/32/185_2.png) [@gawie](https://community.linx.software/community/u/gawie)
#### Post date: [September 11, 2017, 7:16am UTC](https://community.linx.software/community/t/mysql-ansi-odbc-driver-fails-under-certain-conditions/183/1 "2017-09-11T07:16:47Z")

</div>

Use the MySql Unicode driver when using 64bit Odbc. The Ansi driver fails under certain conditions.

**To replicate the issue**

Create an ExecuteSql function that uses 64bit Odbc to target MySql. Execute an insert query that contains a string parameter followed by a decimal parameter. It fails with no error message.

This fails  
`insert into `NameValues` (`Name`, `Value`) values (@{String1},@{Decimal1})`

but these work  
`insert into `NameValues` (`Name`, `Value`) values (@{String1},@{Decimal1.ToString()})`  
`insert into `NameValues` (`Name`, `Value`) values (@{Decimal1},@{String1})`  
`insert into `NameValues` (`Name`, `Value`) values ("abc",@{Decimal1})`

We tracked the problem down to the conversions the Ansi driver does when it makes the call to the database.

**Solution**  
Use the Unicode driver.