You're referring to two ways to use browse mode, correct? (Browse is both a "read" and "edit" mode in filemaker).
There are two methods I am aware of to setup this type of separation:
1) Use different layouts for reading and editing. On the reading layout you set all of your fields to not allow entry into the fields for browse mode (this restricts user from making changes on that layout). Your "edit" button would then change layouts to an "editing" layout, where changes can be made. A "save" button then returns them to the "reading" layout.
2) Access privilege restrictions. When you create a customk privilege set, you can set privileges on any table for editing. There is a drop down under the edit column where you can choose "limited". This then allows you to set a calculation for when editing is allowed (IE $$mode = "edit" ). You would then set your "edit" button to set a variable named $$mode as "edit". And a save button to set $$mode to "read"
Hope this helps!
A third and simple way is to uncheck Field Entry in Browse Mode in the inspector and then have a button that executes a Go to Field [name] step. This is good if you are just interested in a single field but if you want to edit multiple fields, Mike's way is better.
If the field entry is unchecked though, I thought it threw an error if you tried to use "go to field", that seems like a security risk if you uncheck that field for entry and it can be bypassed.
There is no error for the go to field. Not sure what the security issue is. The original question asked for help on how to click on a button to edit a field that you could not normally enter.
"Allow Entry in Browse mode" is not a security feature.
Go to Field does place the cursor in the field regardless of that setting.
Thank you for everybody....
The best way for me was to create a custom privilege set, where I put "limited" to some fields.