This is a known issue.
For More Information see: Portal filtering: <> versus ≠ operator (not equals)
This is one of many acknowledged bugs that can be found in the Known Bug List thread here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: https://www.dropbox.com/s/jt09b82i0xijbu3/FMP%20Bugs.zip
Well how about that.....
Strange how I was not able to find or perform a search on "portal filter" and see that this was already submitted.
Thanks for letting me know.
Difficulties in searching the forum for specific issues are why I started sharing the known bugs list database. I found it there by specifying FMP 12 and "Portal" in the search form.
Thank you for posting.
I apologize for the delay in response. This issue was previously reported to Development and Testing as PhilModJunk already alluded to.
I would also like to alert you to the fact FileMaker 12 v2 was released. Although the update may or may not fix your issue we strongly suggest you update.
If it does fix the issue, please post back so I can update the known bugs list accordingly.
With the 12.0v2 Update I find that neither the <>, nor the ≠ Operators are working.
According to the changelog, the <> Issue was addressed in the update.
I cannot reproduce this in Filemaker 12.02 on Windows XP. For me, either expression correctly filters the portal records.
After testing this out on a portal that I know worked previous to the v2 update, Like Fabian, I'm now not able to see any lines using either the <> or the ≠ operators.
So now it's worse than before, because I can't use the portal filter feature anymore. Now I have to enter the filter conditions in the relationship, which stinks.
In another thread, a poster discovered that if the solution is hosted by FMServer, and the client is FMP 12.02, neither expression works. It looks like an update for FMServer is needed to resolve this issue for cases where the file is hosted over a network.
Apparently this is no longer a problem when applying the recent FM Server update 12.0.2. Any client running either version of 12 (12.0 or 12.0v2) can now view the portal filtering as expected.
Something that I don't understand is what this problem had to do with a Server upgrade, and why the release notes for the update didn't mention this fix??