Your result 2 ("0", I get records with numbers containing zeros) suggests a possibility that the field being searched is text, not number. Is that possible?
Double-checked them, and they are, indeed, all number fields. Thx for the idea.
MORE INFO -- After more play, I discovered something new. It turns out that searching for "0" (or "0.00" or even "$0.00") finds all records that have ANYTHING in them. In other words, the same results as when searching for @*, which, by the way, also works with the reduced permissions.
(Tried one other thing as well -- making the layout modifiable (grasping at straws??) -- but it had no effect.)
But, you wrote
Field-1 in the portal is a calculation that is simply equal to the value of a summary field (total) in Table-3.
calculation field is not number field. check the result type.
And usually referring summary field from another table don't work, since there is not found set and sort order.
Do you want grand total of Table-3 ?
Sorry, wasn't clear. Field-1 is a calculation whose result is a number.
Using a calcuation field that refers to a summary field in another table has worked just fine for us (with [Full Access]). We have used this particular situation a lot and never had a problem. It totals dollar amounts from related records from Table-3. (The level of indirection is necessary for a reason that would require too many words to go into here.) But, you may be on to something, in that the complex nature of the process is requiring something deep within Filemaker's permissions structure. Can imagine, though, what it would be...
If you want total of 'related records', usually Sum(Table-3::someNumberField) is enough, no summary field is needed on Table3.
Summary field in anather table is used in portal, especially it is fitered.
I found now that you wrote
searching for @*,
- ">0", I get no records found
- "0", I get records with numbers containing zeros.
searching for "0" (or "0.00" or even "$0.00")
If the field is number, don't use "" in find criteria. (Sorry if you already doing so)
No quotes were ever entered during the search attempts. (A descriptive convention used inconsistently...)