data protection using calc field

[Chuck]

If you want people to not be able to edit a field but able to enter the field to copy information or perform a find, then a calculation field is the best option I know of. If the fields will be searched on, you might as well set them to be indexed when you define the fields so that the first time a user attempts to search on them they don't have to wait for them to be indexed.

Chuck

[Razumovsky]

Here is another one:

Currently, I use multiple layouts (one with "do not allow entry into field", the other with that option available) for display and editing/input.

I have been toying with the idea of using a layout comprised of all text calculation fields as the primary cust info viewing screen so that sales people do not accidentaly alter info. (the calc being simply the text field) I believe this would let people easily copy info to the desktop and do complex finds without resorting to multiple layouts. One drawback, of course, would be the increased calc. time and file size.

Has anyone tried this, or can point out some obvious flaws in the method?

Thanks!