Find not working across relationship

[mzarin]

I'm working on a system with lots of files, relationships, etc. but am stuck on one interaction in particular. Parent file (People) and child file (Registrations) related by PersonID. Users can see related parent data from the child records, but searches on those parent fields are failing. For example, user wants to search for all Reg. records for person with last name "Kong" from a form layout showing data from People|PersonID::name_last. User knows there are plenty of "Kong" Reg. records, in fact they're looking at one right now, say. Result: No records found. User can go to People file and successfully search for last name = "Kong". But not from Reg.

Any idea what's going on, or how to fix this?

-mz

[ernst]

Hi Mz,

If the relation to Registrations depends on a calculated value on one or both sides of the relation definition then the find won't work, because in find mode the relation will not be valid.

Could this be the reason that it does not work as you expect?

Regards,

Ernst

[Anatoli]

If in Reg is not record with KONG, it will not found one.

[mzarin]

Hi Ernst and Anatoli,

I wish it were that simple! No, the relationship goes from data field to data field (both of type = number), with no calculations involved. And the problem is, I _know_ Regs exist for Kong.

Some results from testing:

- Creating a fresh version of the relationship in my Regs file doesn't work.

- Putting related fields on a fresh layout doesn't work.

- I can create a brand new file, relate it to Person via PersonID, and the search-across-relationship works in the new file.

-mz

[Ugo DI LUCA]

If in Reg is not record with KONG, it will not found one.

The answer is HERE !

Record for KONG IN Reg ----> Nope

Record for KONG IN People ---> Yeah

Regs exist for Kong ---> Good, but useless

Because you're still making your find IN Reg....

Then remember

"If in Reg is not record with KONG, it will not found one."

[mzarin]

Ugo DI LUCA said:

"If in Reg is not record with KONG, it will not found one."

What I'm saying is, even when I know for a fact that a person (e.g. "Kong") has a Reg record, FM is not find the Reg. record when I search on that person's name.

Any suggestions on how to narrow down what's wrong or fix the problem, short of rebuilding the Reg. file from scratch?

-Mike

[Ugo DI LUCA]

The title of your thread says it all....

check this thread

and

Even if you're not performing a find in a portal, check the article from DJ in the Article section, title - Find in Portal

[Ugo DI LUCA]

In France, we use to say something like "Never 2 without 3" ...

If in Reg is not record with KONG, it will not found one.