I have a particular issue with trying to perform a find for a record through a field that is related from another database. I have not had any issues with a previous relationship I had, but then I created a new relationship to another database and when I attempt to perform a find through that, I get a "No records match this request" error message. The data does exist, but I cannot find the records with that relationship. Again, the earlier relationship I set up still performs the find correctly.

Any thoughts?

Thanks in advance.

I'd also like to add that I just found that if I use the same file I'm having issues with and used a different field to relate it to, it works fine. The difference in the field used for the relationship is that the one that does not work is a calculated field, whereas the one that does work is just a normal field. Does anyone know why?

There are specific requirements for using calculated fields as relationship keys. The calculation needs to be based on local fields and not related fields, also the key in the related file can not be a calculation. It sounds as if the calculated key is the culprit.

Generally Filemaker will not allow you to make a mistake like this, but if you create your relationship, and then edit the calculation, you can get in trouble.

honor,

If the field is un-indexable (unstored calculation, ralated field based on another related field, etc), it's unsearchable.

glory

Unstored fields *can* be searched. But it's very slow because FMP has to evaluate the field's value for each record, one record at a time. If there are a lot of records you'll sit and watch the progress bar for a while.