Data changing from Sybase Table
Posted: Fri 20 Nov 2020 20:39
Hello,
I am using Devart's ODBC driver for ASE to connect to a Sybase database, using an ETL app called Easymorph. But i realized some of the data was changed from its original value on the table. It happens on two columns which have data type "money". The issue I have is with negative values between -1 and 0, they are being changed to positive.
When I realized the issue I made the extraction 3 more times, and I noticed only the extractions via Devart's driver had this issue.
1. I extracted the data with easymorph and microsoft access and I had no rows with numbers between -1 and 0.
2. I extracted the same tables using native drivers for sybase, using DBeaver and a proprietary extractor from my enterprise, and the info was correct, showing numbers between -1 and 0 where it should.
I don´t know what is causing this problem, and I think it´s a very particular issue since I could not find any post with a similar problem. Has this happened to anyone? Is there a configuration I have to change when creating the ODBC DSN in order to fix this?
Thanks!
I am using Devart's ODBC driver for ASE to connect to a Sybase database, using an ETL app called Easymorph. But i realized some of the data was changed from its original value on the table. It happens on two columns which have data type "money". The issue I have is with negative values between -1 and 0, they are being changed to positive.
When I realized the issue I made the extraction 3 more times, and I noticed only the extractions via Devart's driver had this issue.
1. I extracted the data with easymorph and microsoft access and I had no rows with numbers between -1 and 0.
2. I extracted the same tables using native drivers for sybase, using DBeaver and a proprietary extractor from my enterprise, and the info was correct, showing numbers between -1 and 0 where it should.
I don´t know what is causing this problem, and I think it´s a very particular issue since I could not find any post with a similar problem. Has this happened to anyone? Is there a configuration I have to change when creating the ODBC DSN in order to fix this?
Thanks!