Case Sensitivity In Queries Linked to Oracle Database

[mcl]

Some time ago I asked if there was a way to get around the fact that queries
became case sensitive when linked to oracle tables.
No one answered so I assumed the answer was no. The other day I stumbled
across the strconv function. Got it out of a PC Mag article on excel macros.
Tried it and it works great. So none of you so called access gurus could
think of that?

 

[Lynn Trapp]

I don't remember seeing your original post, but you should consider that the
problem arose from the fact that the default of some later versions of the
Oracle ODBC drivers were case sensitive. Here's a quote from Oracle's
documentation:

"SQL_ATTR_METADATA_ID attribute. This attribute is an ODBC 3.0 feature which
is used to specify case sensitivity on arguments of the ODBC catalog
functions. For example, if SQL_ATTR_METADATA_ID is set to SQL_TRUE then the
case of the TableName argument of the function SQLTables is not significant.
The default value, as defined by the Microsoft ODBC specification, is
SQL_FALSE (case sensitive)."


--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html