Lookup matching problem
Jaime Perry
jaime at hoovercs.com
Wed Jun 25 11:16:11 PDT 2008
Hello,
I am in the process of copying data from an existing Filepro system to
our in house Filepro based software. To do this, I am doing a lookup
from the old file to our file. Both files have item # as the key
field. Ours is defined as (15,allup) and the original is defined as
(14,allup). My lookup looks like this: lookup new = (fn) k=ky
i=A -nx
FN is defined so it can handle inputed qualifiers and index A is built
on item # with a length of 15. The item number is the first field in
both files and ky is defined as (15,allup).
The problem is for item # DDJNR-2020J-15. When it hits this item, it
thinks the item already exists (which it does not). If I ask what my
key is (ky), I get the above number left justified with a blank at the
end. But, if I ask what new(1) is, I get DDJNR-2020K-15 also left
justified with a space at the end. I originally used field 1 in the
lookup but thought the length differences might be causing the problem
so I switched to sticking the item # in ky to make them equal. This
made no difference. For the life of me, I cannot figure why it thinks
this is a match. Any suggestions would be great.
Thank you
Jaime Perry
More information about the Filepro-list
mailing list