In Filemaker 11 and previous versions, I was able to put in the name of a Start-up Script to set up globals, etc. When I converted one of my systems to FMP 13, that option no longer exists.
Is there some way to do this in FMP 12 and beyond?
Still an option in FM12 - FM14. Select File, File Options, Script Trigger, OnFirstWindowOpen, then select your script.
The Starter Solutions that comes with FM has startup scripts usually named "Trigger | On First Window Open" which is activated by the OnfirstWindowOpen Script trigger.
These are databases that are used on the web - does OnFirstWindowOpen apply to when the database is opened via the Admin Console???
The script runs when a client opens the database. It runs for each client that opens the database.
Global fields have changed from FMS 11 not the startup script.
Setting global fields in a FileMaker Server session | FileMaker
What do you mean opened by the admin console? Admin console usually refers to the FileMaker Server Admin Console. If that is what your talking about then simply hosting a file on server will NOT cause the trigger to fire.
It will fire in any situation where the file is opened including webdirect
There still seems to be a confusion. I have a few systems that are served on the web for which I used a start-up script to set up globals - if you are saying that I need to set up globals another way, that's fine-will follow-up on that.
The start-up scripts that I used to use were run when the database was opened on the server (no client is really opening the database when using the system on the web) and all globals were setup. My question was how to replicate that functionality, but from the answers here, it looks like I need to handle this function another way.
Yes a client is really opening the databases when using the system from the web.
OnFirstWindowOpen is still supported in the startup script. Page 16 of the Web Direct guide talks about using a startup script : https://fmhelp.filemaker.com/docs/13/en/fm13_webdirect_guide.pdf
You have not stated the issue you are having except that it relates to global fields. It may help if you post a screen shot of your script and explain what you expect to happen and then state what is happening.
I read the info on setting up globals by sessions. However, I really want globals to apply to all sessions so I will change my approach to the problem.
I use Custom Web Publishing, not WebDirect (it doesn't support some of the things that I need).
Basically, I was setting up the basic email settings by running one script at start-up for all records.
Thanks so much for your help.
Retrieving data ...