I often use StoredProcedures with Ref_Cursor parameters to read data from an Oracle 11g DB.
Because we use VARCHAR2 columns in our tables, we have to pad blanks for an exact match, the Input Parameter has to contain the blanks for example "WW2 ",
This was working fine over the years using the Microsoft-Ado Provider MSDAORA ( with Excel 2003/10, VBA ).
Now we want to use the Oracle ORAOLEDB Provider. In our tests all resultsets were empty(rs.EOF/rs.BOF)
The reason is, that inside the StoredProcedure the Parameter value was trimmed ( "WW2" ), and so the Where-Clause doesn't match.

Is it possible to change this behaviour( bug or bad feature ? ) by setting a property of an object , in registry or somewhere else ?


Best regards