Why is a drop down list not an option? (Maybe there's a way to get them to work that you haven't considered)
As long as this isn't a field used for WebDirect clients, you can hide a popup menu formatted copy of the field behind an edit box formatted copy of the same field. Use behavior settings on the edit box copy to block browse mode access. If you click on the visible field, the mouse click causes the hidden pop up menu copy to pop to the front and display your value list. (this trick is often done with drop down lists as a way to hide the "ID" value by putting it behind a related "name" field from the value list's table, but it should work the same for a pop up menu formatted field as far as I know...)
I often use this trick (even with tree fields one on top of the other). But in this case it's not practical: when the user releases the pop-up menu, the field with the pop-up comes to front and the arrow (or the empty space of its button) hides the data he has already entered.
I know, I can just code a commit script and fire it on object change.
But why on earth we are not able to get rid of that button? When will be able to code simple solutions? We are always adding tons of objects and scripts to workaround stupid problems.
If you want to complain about a shortcoming of FileMaker, post in feedback. If you want assistance on how to work around the shortcoming, post here.