Just a general question that has nipped at me for years, and am just curious: for the Notes client (not on web), if you want to hide a field on a form completely (e.g. regardless of edit mode, etc.), you access the field properties and then check the “Hide Paragraph From Notes R4.6 or later” box. However, I have seen multiple fields that are intended to do the same thing, but instead of that box checked, it is NOT checked, and instead, ALL the ones below it are (e.g. Previewed for Reading, Opened for Reading, Printed, Embedded, etc.). That serves the same purpose, but why would anyone check all those instead of just making one check for the “Notes R4.6 or later” box? What am I missing? 
Subject: RE: Preference on how to hide a field on a form?
I can’t think of any reason to waste time checking all those boxes, so if I want to hide something always, I always use the notes/web/mobile checkboxes. I certainly wouldn’t do as ZoomTek suggested, though, and write a formula of 1. Any formula takes longer to evaluate than just testing bits in memory, so the form will perform better if you avoid using formulas unnecessarily.
Subject: RE: Preference on how to hide a field on a form?
Once we’ve got you here in a discussion about it:
Why are there still two boxes that can be ticked, after the notes/web/mobile checkboxes are marked? Backwards compatibility with pre-4.6 clients? Would ticking them (or not) make any theoretical difference on a current client, performance-wise?
Subject: RE: Preference on how to hide a field on a form?
Why are there still two boxes that can be ticked, after the notes/web/mobile checkboxes are marked? Backwards compatibility with pre-4.6 clients?Probably. Not that there’s a big demand for that these days, but we do still have some V4 compatibility things in effect, like $Actions item in design notes.
Would ticking them (or not) make any theoretical difference on a current client, performance-wise?
I doubt it. I expect there’s a word of bits in the paragraph definition and we’re just “and-ing” it with a word describing the current situation, hide if any of the bits match.
Subject: Preference on how to hide a field on a form?
you are right… I think it is about habits…
I usually check “hide paragraph when formula is true” and write 1… 1 is always true… and the paragraph will always be hidden.
Soren
Subject: Readability
I always (well almost always) resolve the hide when to @Ture or @False. So if I want to hide a field, or text all the time I just set the field to @True. As others have pointed out you could set the Hide-when ti numeric One. However, You never know who might be reading your code so I prefer clarity over a little efficiency. In addition I prefer using a formula so instead of MyField = “Something” I prefer @If(MyField = “Something”;@True;@False).This has helped me particularly when I have gone back weeks/months/years later and need to figure out what I was trying to do.
I started programming on an Old Univac mainframe with 8K of core memory and we had to be very cryptic in everything, but today I take readability over absolute efficiency, but that is my preference and with todays computes the speed difference between evaluating 1 or @True is not even measurable.