Which version of FileMaker are you using? There's been a recent issue report with FileMaker 12 that would seem to fit what you are reporting here.
You may want to replace your merge fields with regular data fields set in Field Behavior to deny access while in browse mode.
I did use regular fields, but it was very frustrating to get the the "give up" point. There should be a list of bugs somwhere.
What do you mean by "give up point"?
There should be a list of bugs somwhere
I can just hear long time forum users chuckling at that one. Several years back, I felt the same way and set out to create just that. This thread lists bugs for FileMaker 12 and also versions 10, 11: Known Bug List
Recent forum format changes that break this list up in to pages have made this list very difficult to search, but you can also download a database copy (It's a zip file with both fp7 and fmp12 format copies in it) from: https://www.dropbox.com/s/jt09b82i0xijbu3/FMP%20Bugs.zip
Ah, admittedly I've been away from the forum (and FM) for a few years. I should have known.
I meant "to the give up point". I played with the problem for hours thinking I was doing something wrong. That was when I posted originally.
What was the purpose for using merge fields in the first place? If your portal has the typical "mini table" set up, I'm having trouble imagining why you would want to use merge fields instead of regular fields. If you've resized the portal row so that it is more of a "mini form", then there can be formatting advantages to the merge fields.
In the latter case, you may be able to get merge fields to work if you resize them to fit. I learned this trick here in the forum:
Take the text shown in red in the following example and resize it to a much smaller font size. Leave the black text set to the font size that you want:
Hmmm, come to think of it, haven't tried this trick in 12, only in v10 and 11. Let me know if it works.
I suspect that this behavior change came as a result of another rather nice change that they made. In 12, if you drag a portal to reposition it, the layout objects in the portal row move with it. This is very nice and matches the behavior of a tab control, but like the tab control, the layout objects are only "owned" by the portal if they are fully enclosed in the portal row.
Nice tip, the reformatting in <<TableOccurrenceName::FieldName>> does work in 12. Very nice.
I did notice that fields beloing to the portal now, also very nice.