I cannot reproduce this error on Windows Vista SP2 (32 bit).
Do you have any other PCs you can test your file on?
Looks like it may be related to Windows 7 or 64 bit.
TS_Oz, FileMaker Inc.
I can't reproduce this with XP. I tested with the same named folder separate from the same name layout and also by placing the same name layout inside the folder.
I cannot replicate this in FM 11 on either XP or Windows 7 (64 bit).
Just to be clear -- it is on the FM 11 machine where this is not working? I can envision a scenario where you've set up the layout folders on an FM 11 machine and then your Go To Layout step would absolutely fail if run on any version prior to 11.
I tried with an XP machine with FM11A, FM11 and I get the same error.
Here's a better description of the configuration.
- Two separate files using the separation model.
- The files are hosted on a FM11S (not advanced).
- Scripts run on the separation model.
- The folder and the layout are not shown in the layout menus.
- The folder name is "PROPNET" and the layout is "propnet".
- The non-working script step is "Go to layout ["propnet"]" where the step use a calculate layout name.
- I'm using FM11A to develop.
I will try with a local file to see if I get the same error.
Here is a link to a test file. Just click on "Test here" which simply calls a 'go to layout ["propnet"]'.
Here are the steps I used at first :
- I created the folder named "propnet" directly from the "Manage Layout" dialog, using the dropdown menu.
- Then I created the "propnet" layout clicking on the "New" button still using the dialog.
- Created a test button on the "houses" layout.
- Selected the "Go to layout" using the layout name.
- Go back to browse mode and click save.
I found something interesting. If a renamed both to "abc", it worked and if I renamed them back to propnet the bug doesn't seem to reproduce.
How odd, your file definitely fails on my XP system, but my own file, which appears to exactly reproduce all the same settings, does not.
I even tried changing the case of your folder name as one was all caps and the other lower case. I also tried writing my own script, renaming the layout and folder names by re-entering "propnet" and none of that worked. I tried recovering the file, no problems where identified and the recovered copy had the same issue.
It might be interesting to run your file through FMDiff to see if it reports any issues.
The file that I linked to previously was created under a WinXP environment and local. The first time I notice the bug, the files were running (and still) on a server, used the separation model and the machine was Win7 x64
What is FMDiff?
Weird again, I modified the file that you linked and the bug is still appearing.
Here are the exact steps :
- In layoutA, go into layout mode
- Click in the layout menus and select "Manage Layouts"
- Create a new folder named "test"
- Create a new layout named "test"
- Close the dialog
- Add a label "test"
- Save the layout
- Go back to "layoutA"
- Add a button
- Select script step "Go to layout" and type "test" in the calculation
- Type "Goto test layout"
- Save layout
- Go to browse mode
- Test button --> Doesn't work in my case
BTW, the FMA version is 11.02
Weird is the right word. It's like your copy of FileMaker is cursed or an issue that only happens when the file is modified on a Windows 7 system is causing the problem. I'm also using FMP Advanced 11.02, but on XP.
TS Folks: please download and test the last file. It has one button created by me that works and one created by el_pablo that does not.
Thank you for your post, and I apologize for the late reply.
This problem was previously reported (not by a forum member), and a later post seems to narrow down the cause.
If the Layout folder occurs before a Layout with the same name, then the "Go to Layout" script step will fail (error 105). However, if the Layout name appears in the list before the Layout folder with the same name, it will work. You can see the later post at:
I have attached this thread to the original reported issue. Until this is changed, either make sure no folders match the name of an existing layout, or put the layout before the folder of the same name under Manage Layouts.