SQLGetDescRec returns wrong field data

The RecNumber argument of the function is 1-based, but internal function getting the record is 0-based. That caused shift in results - the function returned data for the next record(and default descriptor data for the last record).
The good thing is that the purpose of this API function is not quite clear, or rather it does not look that useful, and applications out there do not use it. The shameful fact is that we did not have a testcase for it, otherwise we would also catch ODBC-500 long time ago.