Not seeing this problem on 12.0v2 using OS 10.7.4
Created two simple tables, simple one-field relationship, filtered on a hand-entered number field. Are you using a calculation to get a resulting zero, or is it a number field?
I've tried on 12.0v2 on mac and PC, I have the same result. It's a number field with an auto-enter option. I've tried to open the same data on 12.0v1 to check, and it works.
The relationship is really nothing special. I have an enrollment table linked to a payment table. The Filter was Payment::Amount ≠ 0.
What's really strange is that I've tried with a local copy of the database, and I don't have that problem...
The only weird thing I've ever seen with FMPro and the "does not equal operator" is that you should ALWAYS use the widget in the calculation dialog box to enter it. Using your OS-specific keyboard sequence (and you must be on a Mac if you are seeing it as "" and not "<>") will not necessarily translate to cross-platform usage. I can only infer that, under the hood, the character displayed has little to do with the character(s) that FMPro is using to denote the operation.
If you hand-typed the operator, try replacing it with the one from the calculation dialog box 'button' instead.
-- Drew Tenenholz
I always use the dialog box option to enter "≠" and never had a problem before.
But anyways, I've done some testing, and I found out how to reproduce the bug.
1) I created 2 files (1 interface, 1 data). In the data file I have 2 tables, enrollment and payment linked like this:
enrollment::ID <- -> payment::enrollmentID
2) In the interface file I created a layout based on enrollment with a portal based on payment
3) In the portal option I added this filter: payment::Amount ≠ 0
Localy it works perfectly. BUT as soon as I put them on the filemaker server IT Doesn't work with FM 12.0v2 client anymore....
I've just experienced the exact same problem. After updating to 12.0v2, the records in two separate (and important) portals have disappeared. Both portals have straightforward filters, but both using the ≠ operator, which seems to be the common factor. On the same layout as one of these portals I have another with a far more complex filter using calculated fields (but no ≠), which works fine.
I can't believe FileMaker have released a "bug fix" update with such an obvious additional bug! They really need to get their act together!
I forgot to mention that the database is running on a server using FM Server 12, which seems to be the other key factor.
I noticed the same issue when i updated my test machine to v2. I too am running the databse from FMSA12 v1.
The filter i am using is NoteStatus ≠ "Canceled"
I would assume the issue has something to do with the difference in version. Perhaps i can track someone down here at Devcon to confirm.
i am having severe issues with portal filtering in 12v3 posted in a new post ( https://fmdev.filemaker.com/message/106776#106776 )
has anything been fixed in fm12v3 regarding portal filtering?
I've tried the "≠" again, but it still doesn't work.
1 of 1 people found this helpful
I've just tried with Filemaker client 12.0v4 connecting to server 12.0v4, the portal filters with "≠" seem to be working again