Turns on a workaround for Visual Basic/Remote Data Objects (RDO) that circumvents a problem with FORWARD_ONLY cursors when the ODBC Client reports other values than FETCH_NEXT for SQLGetInfo(SQL_FETCH_DIRECTION).
For example, if the ODBC Client only reports FETCH_NEXT, RDO performs SQLExecDirect, SQLBindCol, and SQLExtendedFetch(NEXT). If the ODBC Client supports more than FETCH_NEXT, RDO performs SQLExecDirect, SQLExtendedFetch(NEXT), and SQLGetData. This is only valid when the rowsize is 1, but RDO uses a larger rowsize in this situation.
Valid Values
TRUE | FALSE
If set to TRUE, the driver will incorrectly report that only SQL_FETCH_NEXT is supported, which satisfies RDO.
If set to FALSE, the ODBC Client will correctly report values other than SQL_FETCH_NEXT.
