Single Column Fetch bug(?) with merant ODBC

[sprout]

Merant ODBC progress database single column select problem.

Hello everyone!

I seem to be encountering a very strange problem when trying to select a certain column from a 3rd party progress database through merant's ODBC driver. Up to know, I have not been experiencing any problems of this kind with this particular database. What happens is this (column names replaced for clarity reasons):

When I do "select * from someTable where columA = 4301 order by columnB asc" I get the expect results for columB, but when I do "select columnB from someTable where columA = 4301 order by columnB asc" I get totally different results for columnB. Instead of 200302 (the expected number) it suddenly becomes 848273!

It doesn't matter if I include the where-clause and ordering or not, somehow the integers shift from the 199903-200302 range (integer representation of months) to the range 848273 to 848773!

This happens both when I do it programmatically or when I use a third party ODBC client (SQL Explorer or Query Tool 4.1). Am I missing something obvious? The column at hand is an integer (allow null) column.

According to my ODBC Driver Info, I am using:
1. Progress 09.92.0B00
2. Driver ODBC 3.51
3. ODBC 3.52

I would be very, very grateful for any insight or enlightment!

 

[sprout]

Well, for now the problem seems to be solved if we fetch one specific extra column. Nothing special about this column either (varchar), but if we include it the contents of columnB return to normal. Yay.