I'm using windows, so that may explain the difference.
On a filemaker file hosted by server 10, using filemaker 1 advanced, I can click or tab into fields grouped with layout text as long as they aren't set up as a button.
If they are set up as a button to perform a script, I can no longer click into the field--filemaker has always worked that way to my knowledge. The button setting intercepts the mouseclick so the cursor never get's placed in the field.
However, I can still tab into the field and edit the contents as long as the field is part of the layout's tab order.
Thank you for your reply. You bring up a good point. I can certainly ungroup all objects until I get the warning that an object is defined as button since a text field is generally not defined as a button. I am still curious why FileMaker 11v2 won't allow me to enter into any text field when is has been grouped with other objects. That has always worked in prior versions. I am wondering if this behavior has to do with the new security features of FileMaker 11v2. Thanks again.
I don't think it has anything to do with any security features. The behavior of Filemaker 11.02 is unchanged on my Windows system.
Can you confirm this happens with a brand new file? (Create a new file, define a few fields, group some with the field label text and test...)
That will rule out the possibility that something is wrong with the file itself.
I could not replicate the issue with a new file that had one text field grouped with one object. It is also worth noting that the file with the issues never had any problems and continues to work flawless in FileMaker 10. After ungrouping all object on one layout in FileMaker 11v2 every text field on that layout work flawless as well. I would love to find out if anyone else experienced similar issues. Thanks.
Sometimes file damage affects different versions of the software and/or different OS platforms differently. Often, hidden file problems come to light after a version upgrade.
I'd replace that file with a backup that doesn't show this problem if it is at all possible. If not, you might want to rebuild the layouts where this occurs just to be on the safe side.
Due to this recover bug: FMPA 10: group graphic + align = corrupt file?
Many developers avoid leaving any layout objects grouped if they can possibly do so.
Thank you very much PhilModJunk. The link about the recovery bug was very informative. I made extensive usage of resizing and aligning grouped objects during development. You have been very helpful.