A database will open to the last layout it was on when the file was closed in a local (i.e., non-hosted) environment. Therefore, to manipulate this, you can:
1) Unhost the file and download it to a local hard drive.
2) Place the context on the desired layout (and appropriate window size).
3) Close the file.
4) Upload it to the server.
Many developers use an OnLastWindowClose script that accomplishes these tasks so we don't forget during development.
Further to Mike's post, you could use the OnLastWindow close script to navigate to the layout you want to open on as the last step before closing the file. That way your file will open on that layout instead of the default one as you are experiencing.
This will only work if you run this closing script while the file is in a single-user unhosted state. Once it's been put on the FM Server, it's stuck, and scripting the closing layout at that point won't fix it until you take it off the server and re-open/close it.
Yes, that’s why you do it early on in development (i.e., before you host it).
OK thanks Stephen and Mike. Another little bit of learning for me.
My app is a stand alone app.
When I run my startup script, the first thing FM does is open an existing Window.
Besides giving that window a TEMP name, opening a new window, loading my layout
in that 'new' window and then closing the TEMP window... isn't there a more elegant
way to get FM to just open a new blank window WITHOUT opening the TEMP window?
Did you set file option "Switch to Layout" ?
Bada Bing! Bada Boom!
Thanks for pointing out this feature. I have worked with FM for years and never noticed it before.