Criteria error

  • Thread starter Thread starter Darin
  • Start date Start date
D

Darin

In Access 2003 I was using the following criteria to quickly find a record.

Like "*" & UCase([Please enter first name]) & "*"

I only needed to put in a few letters, and access would find all records
that matched the criteria I was prompted to input in that field.

I have since upgraded to Access 2007 and now get the following error when
trying to use this criteria.

ODBC --call failed.

Why would it be looking for an ODBC connection . . . ?
 
Where is the table in question? Access is seldom case sensitive and wouldn't
normally need the UCase function. However some other databases, such as
Oracle, are. Could this table be linked to another database by ODBC?

If not, I'd try getting ride of the UCase() function.
 
This query is feeding from a linked table via an ODBC connection in another
database. The data in the other database is in all caps.
--
END


Jerry Whittle said:
Where is the table in question? Access is seldom case sensitive and wouldn't
normally need the UCase function. However some other databases, such as
Oracle, are. Could this table be linked to another database by ODBC?

If not, I'd try getting ride of the UCase() function.
--
Jerry Whittle - MS Access MVP 2007 - 2009
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder

Darin said:
In Access 2003 I was using the following criteria to quickly find a record.

Like "*" & UCase([Please enter first name]) & "*"

I only needed to put in a few letters, and access would find all records
that matched the criteria I was prompted to input in that field.

I have since upgraded to Access 2007 and now get the following error when
trying to use this criteria.

ODBC --call failed.

Why would it be looking for an ODBC connection . . . ?
Click to expand...
Click to expand...
 
Back
Top