Is your find criteria correct? Did you enter a value that you know exists in parent name?
Are you executing the find from the correct layout context? should be performing the find from the child layout that is bound to the right child TO.
Does your child table have records?
Does your child records have valid FK values to parent?
If you go to the child layout and execute a good find on parent name field it works.
parent_find.fmp12.zip 65.0 K
Check to make sure that _pk_customer_id (in the parent table) and _fk_customer_id (in the child table) are both of the same type (text or number).
Also, are you sure that the _fk_customer_id fields were populated with the corresponding value from the parent table? If the child records were created in a portal from a layout based on the parent table (where the "Allow creation of records in this table via this relationship" was selected) then this would be done automatically. However, if you create records manually in a layout based on the child table, you have to manually set the _fk_customer_id value.
I will follow the instructions you have provided and check what i'm doing wrong
I will keep you updated
Thanks a lot!
This sample makes it easier to find the problem in a small scale, this is really appreciated!
Dear Goldencode --
As other have mentioned, you have to have child records to search for and they have to be linked to the parent table properly.
But there's another slightly strange thing that could be going on with the search, the @ character in email addresses.
FileMaker treats the "at" character as a wild card in searches, and uniformly fails when you search for the string "email@example.com" (without quotes). You can get around this by typing "my_email\@domain.com" (again without quotes) as the search criteria. That little backslash tells FileMaker, "no, I don't want the wild card @ symbol (any one character), I want you to find an actual @ symbol. The backslash works for all sorts of 'special' characters, including the double-quote and anything you see in the 'operators' menu when you are in Find mode.
It is a matter of some puzzlement to me that when using the @ without the backslash, you'd think it would mean any one character, but apparently not the one character that would be useful, the @ character itself, but this behavior has been consistent over many versions now.
Your mention of searching an email field made me think this might the issue you have.
You can also include your search text in quotes to keep characters such as @ or # from being treated as search operators.