If you are thinking about upgrading to FM13, this would be a good reason because you can easily hide things in 13.
If you stay in 12, have you tried using a tab panel and control which panel is shown depending user access? You could also use field access control in the account security settings.
I'll second Todd's suggestion on using the security settings. Regardless of what interface tricks you use, if you really don't want the users to see the data, the security model should be leveraged.
Upgrade to 13 is not an option at this time. The criteria I am using is a person can not see contact info on records they are not assigned to.
This would be much to difficult to do via account security.
I will try putting a button or other object over it next....
Of course, I don't know all of the particulars about your solution, but the same calculation you use to control the conditional formatting, etc. can probably be applied to control the field access. I use it for the exact purpose you describe to prevent salesmen from seeing data from customer accounts they aren't assigned to.
If you are just going to simply cover the field be aware that user can still tab into it so the OnEnter trigger will still be needed.
Agree. And take it out of the tab order.
That sounds what I want to do. Salespeople can only see the phone number email etc if they are the assigned salesperson or if it isnt assigned, and if the feature is turned on as an option.
So I collect all the variables and you then put that as a formula on that field in the security area?
Yes, however it will affect the entire record. I'm not sure if there is a way to conditional control the access to a specific field using the security settings.
This Filemaker Forum is a mess. Once again I cannot reply on the page, forced to reply by email. Can't start a post using IE, text is white and wont post. For a tech company this is embarrassing, really terrible!! Just saying
I think I will just take all the fields I want off the layout, then add a button that pops it up with the security in the script controlling the pop up.
I ended up adding a tab box to my layout, I split the contact security info to a 2nd tab and then put script trigger on the layout and tab that checks if user has access to the tab they are trying to reach. If they do not they are directed to a differnt tab
I am wondering if the hiding features in 13 are added to a layout. What happens when someone using FM12 or and older version of Go visits that layout?
If the open a file with that uses FM13 hiding in FM12, the objects will be visible. If you use FM13 features in a solution you need to set the "Minimum version allowed to open the file" to 13 the the File Options dialog.
Use the Database Manager and Privileges and choose a Privilege Set.
You can mark the various fields as not viewable or editable. This doesn't make them invisible howerver and may irritate some users or inspire others to feats of grandeur.
I really like 13's ability to hide or show objects based on various criteria. Now I can put a developer popover on layouts and no one but me sees it.
My experience bia back opening the file is that 12 can really mess up a 13 layout. There's an option to prevent 12 from opening a 13 file. Whistle if you can't find it.
Next would be to do what I do as it seems safe to let 12 users open a file if you protect your self:
In every script use an if before going to layouts:
go to layout specifically designed for 12
else if 13
go to layout specifically designed for 13 but not 12
To simplify my life I hard code the name of my layouts
[FORM] TableName (description) 12/13 (iPhone, iPad, PC, Mac, WebDirect)
FORM can be TABLE LIST FIND etc.
Then instead of the above if I have a nifty go to layout by name calculation which is highly classified and top secret.
Maybe I'll make it a custom function to keep prying eyes out...
And this system works really well for buttons and can use the name of the window if I set it to get(layouttablename).
I find that one problem is creating a new tab on my Chrome browser to read a post. The password doesn't go with the new tab and I have to re-enter it.
If I don't create a new tab, then it stays with me.