Search results

  1. R

    Error Filtering on Lookup Field from a Query

    Yeah, I'm at a loss as to why I'm the only instance where this error seems to occur since two of you have now opened the sample file and found no issues... I'm on Version 2409 (Build 18025.20126) if it matters.
  2. R

    Error Filtering on Lookup Field from a Query

    If you have some resources on how to build something that allows for a human readable entry for this case, then I'm all ears. But the Lookup is really just to store a foreign key in the table so they can be joined with queries for outputs. The problem seems to be using the lookup on the query...
  3. R

    Error Filtering on Lookup Field from a Query

    This is the initial setup of a database for cost estimates and I'm transferring data from other sources while also integrating a new coding system for line items. This field isn't intended to retrieve the data from another table--just to relate the data table items with the categorization facts...
  4. R

    Error Filtering on Lookup Field from a Query

    When I filter from String, I get the same code as you see. When I filter by StoreID and accept the error, the field remains blank or unchanged if it was previously filtered by String. When I add the code from your StoreID result and then try to filter it, I get a type mismatch message. The...
  5. R

    Error Filtering on Lookup Field from a Query

    Well that's even more confusing. This is what I get:
  6. R

    Error Filtering on Lookup Field from a Query

    I have a table that uses a lookup to get an item from a query. That query combines two fact tables (a category and its subcategory) in order to create a readable name for users doing the data entry/updating by joining them and concatenating the strings. The SQL checks out and the query runs...
Back
Top Bottom