This has been a known issue even with previous versions of MDAC. MDAC incorrectly converts a DB_Decimal number and in this case they are returning a 96 to the SQL Toolkit. MDAC 2.6 correctly returned an error (along with the incorrect conversion number) and the The SQL Toolkit was able to detect the error and try to fix the problem by checking the format of the DB_Decimal number. With MDAC 2.7, the error is not returned and the SQL Toolkit has no way of knowing an incorrect conversion took place.
Your options are
1) somehow get the 9600 number to be stored as something else but DB_Decimal
2) try a different driver
3) try a different provider
Maybe Microsoft will fix this bug in the next version of MDAC. I'd check their site for updates.
Regards,
Azu
cena
NI