Re: query only returns values if criteria cut-and-paste

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I apologize for the delay in getting back to you. I'm afraid this is not
what's going on here. But, it's an interesting thought.

"John Vinson" wrote:

> On Tue, 21 Jun 2005 07:49:11 -0700, "Tony"
> <Tony@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >using Access 2002 SP3 at work. I am finding that queries are not returning
> >records unless the criteria I enter are cut-and-paste from underlyng table.
> >For example, I need records from an "Activity" table, of the Type "Customer
> >Approval". If I simply type "Customer Approval", I get nothing. If I cut
> >"Customer Approval" from the underlying table, and then paste that into the
> >criteria, I get what I'm looking for. I've had a love-hate relationship with
> >Access for 10 years. This is the first time I've ever come across this.
> >There are no spaces or other characters, e.g., carriage returns, in the
> >underlying data that I can see. Ring any bells for anyone? Thanks.
>
> My guess is that you have fallen victim to Microsoft's abominable
> "Lookup Field" misfeature. Is the Type field a Lookup? If so, what you
> SEE is the looked-up text "Customer Approval", but what's actually
> stored in the table (and required as a criterion) is the numeric ID of
> that record in the lookup table.
>
> John W. Vinson[MVP]
>
.



Relevant Pages

  • Re: query only returns values if criteria cut-and-paste
    ... >records unless the criteria I enter are cut-and-paste from underlyng table. ... >underlying data that I can see. ... "Lookup Field" misfeature. ... Is the Type field a Lookup? ...
    (microsoft.public.access.queries)
  • Re: Make a field lookup dependent on the value in another field of a record?
    ... i think you're correct in your basic grasp of how to use a lookup table via ... your form is based on tblA. ... > A lookup field in a table, based on another table, while it displays the ... > i'll do a quick setup and email it back so you can see how it's done. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Are lookup fields truly evil?
    ... with the related foreign keys in your ... lookup table, and Product.CategoryID is a lookup field. ... The Evils of Lookup Fields in Tables ...
    (comp.databases.ms-access)
  • Re: Are lookup fields truly evil?
    ... lookup table, and Product.CategoryID is a lookup field. ... Very bad design. ... The Evils of Lookup Fields in Tables ...
    (comp.databases.ms-access)
  • Re: Lookup function
    ... install the macro and run it on the table, that will work for the first ... > desired lookup criteria and the formula will not work. ... > 201207) and then paste it into cell E2, ...
    (microsoft.public.excel.worksheet.functions)