Re: Lookup Errors with exact match

Timbo <thook@xxxxxxxxxxxxxxxxxxx> wrote:

> I am trying to lookup value from another file based on a relationship
> which matchs a joined field in two files. The problem is that it is not
> retuning an exact match in the relationship. Therfore returning
> incorrect lookup values.
>
> ie
>
> 172164:3R73A517C44AB6AWA
> Returns
> 172164:3R73A517C44AB6QHA
>
> It matches everything but the last few letters ie AWA & QHA. Is there
> a limit to the amount of characters that can be matched??

You don't mention your version of FM, but because you're looking up from
"another file" instead of "another table" I'm going to guess FM 6.

Your key values are too long without spaces. In FM 6, text fields will
index up to 20 characters per word, but not more. In your example
above, FM doesn't see any difference within the first 20 places, so your
matches are invalid.

The solution is to break the field into several words using spaces. The
colon is not a word-separator in FM6, it is in FM7. Once the spaces are
interspersed, FM 6 will (if I remember correctly) index up to 160
characters for the purposes of relationship matches.

Remember to insert spaces on BOTH sides of the relationship.

Lynn Allen
--
Allen & Allen Semiotics www.semiotics.com
FSA Associate Filemaker Design & Consulting
.

Relevant Pages

  • Lookup Errors with exact match
    ... I am trying to lookup value from another file based on a relationship ... which matchs a joined field in two files. ... a limit to the amount of characters that can be matched?? ...
    (comp.databases.filemaker)
  • Re: Recovery via Unrecovery
    ... pair picks the lookup table. ... with the characters picked out of a hat. ... were always a couple of characters left in the hat after filling the table. ... I had NANAE and ASR mixed up - I thought NANAE was the place ...
    (alt.sysadmin.recovery)
  • Re: VLOOKUP and repeating results
    ... There are spaces or other invisible characters in either the search arguments or the lookup table. ... Use absolute addresses for the lookup table, like $A$1:$B$20 instead of relative addresses like A1:B20. ... | corresponding New Account Number from sheet 1. ...
    (microsoft.public.excel.misc)
  • Re: Recovery via Unrecovery
    ... I used to write my passwords down: 9 pairs of 6-sided dice throws. ... pair picks the lookup table. ... with the characters picked out of a hat. ... were always a couple of characters left in the hat after filling the table. ...
    (alt.sysadmin.recovery)
  • Re: Pep 3105: the end of print?
    ... Python 2.3 and Python 3, ... three look-ups and 16 characters instead of always available, ... lookup, though given the probable time taken to do the I/O, why worry ...
    (comp.lang.python)
Loading