We'll need a lot more info to try and help troubleshoot. Not a known issue AFAIK.
And what tells you that's it's not working? Could it be that data in a match field is keeping related records from matching the way that you expect them to?
Are you updating a very old version of FileMaker and have text fields with long strings of text used as match fields? (very old versions ignored punctuation and spaces where newer versions do not.)
Perhaps you have problems with the indexes of one or more fields--this can cause apparently random failures of relationships, finds and sorts. You might try rebuilding the indexes in your file:
- Take file down off the server if it is hosted from a server.
- Launch FileMaker without opening the file
- Select Recover from the File Menu
- Select your file as the file to recover
- Select the check box for advanced recover options
- Select only: Copy File Blocks "as is". Rebuild Indexes Now.
- Run the recover and test the recovered copy to see if this corrects the problem.
I use portals and when I get that problem, the forst symptom is that the portal is empty, and it should not (i made sure...)
My version of Filemaker that was updated to FM16 is FM14.
I'll try the index solution and will let you know if the problem comes back.
What types of fields are the key fields on both sides of the the relationships that seem to fail?
Indexed Number for all the key fields
OK. Thanks. I was checking to see if there were any calculated fields as key fields. That can lead to some random behavior.
I believe that saving a compacted copy of a file will also rebuild the indices. That saves having to go through the "Recover..." process.
I've been running this solution or 5 years and never ever got a problem before.
Just since we moved to FM 16...
Thanks for your interest.
Saving a compacted copy does not rebuild indexes. Also note that with the options that I recommended, the indexes are the only thing modified.
I understood that you recommended only the reindexing; I was under the impression that saving a compacted copy did rebuild indices, so I was suggesting that as an alternative, that’s all.
But you also said:
"That saves having to go through the "Recover..." process."
We nearly always tell people: "Don't put a recovered file into regular use", so I was clarifying that in this case, given the options specified, it is OK to do that.
I understand. I was referring only to the fact that Save a Copy As is slightly fewer clicks than Recover.
I have exactly the same problem, I'm working with FMS15 and 2 client with FM16, the other ones with FM15 (8 client) are working perfectly, but the ones that have FM16 on their machine have this issue.
Please help I'm going mad with this problem!
Start with providing as much information as you can, screenshot of the relevant part of the graph, some data, anything that could help us think through this or replicate it.