Incredible but true...
I just encountered the same problem and i first thought about an installation error. I performed a search on this forum and found your unanswered post.
I tested it on many systems both Mac and PC, and the results were always the same. I'm on 12.0.3 version that is the last at this time.
Moreover, you cannot use the Duplicate button when [Standards Menu] is selected. Hard life...
PS : I sent a message to TS-Falcon from FMI to check your post. He is very professional and helped me many times.
PPS : If you have FMPA 11, the workaround consist to first create the file with that older version and then converting the file to 12. Please note that starter solutions seems to be OK and you will not encounter this problem.
cant find it at the moment - but this was described as 'changed' somewhere in the 'Help document (sorry for typos - but at the monent, the forum SW on an iPad is even worse than before...)
Sorry but i am not shure to understand your comment. But true, i found 2 lines about the Custom Menu in the v12 News in Help command. That mean a Custom Menu is now supported in FM Go.
Thank you for the post.
The Custom Menu Set 1 that was part of FileMaker Pro 11 Advanced is not included in FileMake Pro 12.0v3 Advanced. Development and Testing are aware of this issue. I've added your comments to the original report.
Unfortunately, FileMaker Pro 12 Advanced seems to be designed lo loose this feature that we appreciated for years before, surely with 11-10-9 versions and maybe previouses, but i can't confirm so far.
Anyways, because i am feeling very sad because all developers must now, like robots, create manually their Custom Menus, I simply did it for them...
So, you can now download empty files that i created in many languages HERE :
Theses files contain an empty untitled table without any field. Exactly like when you use the [new] button on Open file dialog. Please note that they were created with brand new 12.0v4 version. They aren't converted files.
Theses files have the option "Always use the system regional parameters" checked.
With FileMaker Pro, the end-user always see the menu titles in his own system language. However, the developer, when configuring his Custom Menu, is seeing the original language menu. This is the one of reasons why it is important to download your preferred language file version. Another, more important, is that some calculation functions like MonthName ( Date ) get a result that depends of the current regional system where the file was created.
Please consider that it could be a better choice to start your project with a starter solution : File > New from Starter Solution… menu command. Certain Starter Solutions are continuing to bring the Custom Menu Set 1 (like "Contacts" for instance) while other doesn't (like Employees for instance).
Good luck guys...
Without a way to import custom menu sets, the lack of an almost-standard already-built "Custom Menu Set 1" really wastes a lot of time and discourages people from using the Custom Menu feature, since it means a LOT of work, rather than a few quick changes.
The fact that the "Custom Menu Set 1" set was not removed from the included templates indicates that either:
1) the lack of "Custom Menu Set 1" in a newly-created empty file is a mistake, or
2) FileMaker engineers made an affirmative decision to remove this for some inexplicable reason and forgot to tell the template designers it should no longer be included.
I hope it is #1, since option #2 would be very discouraging. If it is #1, then this is basically a bug and should be fixed, hopefully in 12 as well as in 13.
This issue has been addressed in FileMaker Pro 16.
Could you be more precise ?
As far i know, the original poster description is still true with FMPA 16.0.1.
I agree with Fred(CH)
If I create a brand new solution, I still need to recreate all of the Custom Menus manually, and then bundle them together in a Menu Set.
The this was the same in FMPA 15 also.
I'm agreed with Fred and Jerry. I see no way to get a complete custom menu set without building it manually. Very painful.
My apologies. This feature request was posted as implemented in FileMaker Pro 16, but I have received verification that this information was incorrect.