hello,

i have the following simple relationship:

file1::partnokey --> file2::partnokey

in both files, the match field is a calculation -- partnokey = left(upper(partno),11) --these fields are also indexed.

both of the following "parent" records will show the same set of related records from file2:

file1 record 1 -- partnokey = 21BAA0001A_

file1 record 2 -- partnokey = 21ZXX0001B_

RELATED RECORDS FOR BOTH

file2 record 1 -- partnokey = 21BAA0001A_ / quantity = 1

file2 record 2 -- partnokey = 21BAA0001A_ / quantity = 3

file2 record 3 -- partnokey = 21BAA0001A_ / quantity = 7

can anyone tell me why it does this? how do i get around this?

any help would be greatly appreciated!

thanks,

Derek

Hi,

Make sure the calcs are indexed

thanks for replying. yes, my fields are indexed, so that's not it...

Hi again,

Check your portal relationship and check also the fields in portal. They must come from this relationship...

thanks again. yes, everything seems to be in order. upon further investigation, it seems as though FM is matching based on a "pattern." any parent with partnokey = "21***0001**" finds the same children (listed above).

[where * = a character A-Z]

in a parent, if i change one of the letters (where a * appears) to a number, it doesn't find any children. but any combination of letters where the * are find the same set of children!

i dont get it.

thanks

Derek

OH!!

Turn the Num to NumToText(yournum).... and turn it to be a text_ID

Thanks. I solved the problem. The fields were defined as "calculation" - i changed it to "text" and now it works.