Back to COM and ADO.

It’s all about COM component that scrabbles given string and insert the results into oracle DB. That component is working for a 6 month but for time to time the results that stored in the DB found corrupted when tried to re-scrabble by other application. The guys that wrote that component try to find out what the reason for this unexpected behavior without any success they saw that they writing ASCII values to the DB but for some reason the values that saved in DB didn’t match the send values. Further study found out that the oracle driver – ORAOLEDB, for some reason, don’t like values between 0xC0 – 0xCD and always replaces them with 0x63. The only workaround that we found is to use Microsoft provider MSDAORA. MSDAORA doesn’t seem to have this problem.