We recently changed our PC environment to remove all Oracle clients prior to Oracle10 (some PC's had three or four Oracle clients on them with different Oracle homes). In doing this change, we also removed all prior versions of Oracle ODBC drivers. For the most part, everything is working fine.
However, one peculiar thing I've seen is that a query on an Oracle table that is being run through an Access link used to work, but now it seems to require that we specify a trim function on the query fields to get it to work without forcing the user to blank fill the query input fields.
Here's the SQL for an Access query that used to work, prompting the user to input a value for the "System" field:
SELECT * from TABLE1
WHERE (((TABLE1.SYSTEM_CODE)=[Sy
stem]));
System_code is a 6 Char field.
Before, for example, if the user put in just RHR in response to a prompt, the query would return the expected rows. Now, however, this query does not return any rows. To get the query to work, the user has to either enter RHR followed by three blanks, or the query has to be modified to be:
SELECT * from TABLE1
WHERE (((trim(TABLE1.SYSTEM_CODE
))=[System
]));
With this revised query, if the user just puts in RHR without any trailing blanks, the query performs as expected.
The only thing I can see that changed in the environment is the different version of the Oracle ODBC.
Does anyone know of anything in the new Oracle ODBC (a difference between the Oracle 8 and the Oracle 10 ODBC) that would force the use of the trim function? Or is there possibly something else that happened?
Start Free Trial
