Custom Menus, to be seen or not to be seen...

[phuebs]

I want to create a custom menu for a Runtime App. But I want to see some of the stuff I take out when I'm editing or using the database in Filemaker?

For example, I want to take away the Scripts Menu and the possibility of people looking at or using scripts outside of their database functions in the Runtime. BUT....I obviously want to see the Script Menu when I'm using FM, updating the Runtime, and all that.

Is it possible to do such a thing?

[bcooney]

Yes, just set the file's menus to Standard Filemaker if Get (privilegesetname) = "[Full Access]" in an Open script.

[LaRetta]

It might be better to control the custom menus for all other privilege sets. Maybe it's just me and what I learned today ... when the Developer drops into layout mode then goes back to browse, custom menus takes over again. It is PIB.

[Vaughan]

I set up a whole heap of "base" tables, the ones that the developer sees but the users should never use. These are all set to use the FileMaker Default Menus, and it's taken away the PIB that LaRetta feels.