Since my experience with QODBC is that its too slow for me. Even after i read the articles, that speeds up the link with Access > QODBC wich where verry usefull.

I wrote an program that uses QODBC to fill my MS Access database.
So i can use Access too execute Queries.
It worked like charm, until today.
Access gave an error:
The decimal field's precision is too small to accept the numeric you attempted to add.

I thought the problem was MS Access. So i tracked it down to the ItemInventory table, even the PurchaseCost field.
Google told me the problem should be fixed by modifying the query to something like select purchasecost * 1 ... so the query should round nicely.
That didnt work for me. I tried lots of solutions. Nothing worked.

I thought it might be better to track the record down. I found that in Quickbooks it purchaseCost was set to "12.361,27731". When modifying it to "12.361,28" everything worked as before.

This was nice for me as a workarround. But i would like to see it solved.
I think its some bug in QODBC. Cause changing quickbooks solved the error.

I use regional settings from the netherlands, since i live there ;). But that wasnt an problem before.

I'm using QODBC 7.00.00.192 i noticed its not the most up 2 date version. But i couldnt find anything in the readme from the updates that fixed this error.

If you need more information, please let me know.

Greetings
Johan Toonders

Sorry, QODBC currently only supports the use of a . (fullstop) as the decimal symbol in the Regional Settings of Windows.

QODBC supports "12361.27731".

The QODBC optimizer can be switched off. See: How do I setup the QODBC Optimizer? Where are the Optimizer options? 

Work has been done to support the use of , (commas) as the decimal symbol on output, however INSERT, UPDATES and WHERE statements will need to continue to use . (decimal).

Any news on this topic?
I'm getting more and more errors on importing data.
And the more errors i get, the less information i can use from QODBC.