Perform Script on Server (PSOS)
DayBackForFileMaker.PSOS History
Hide minor edits - Show changes to markup
Note: This may be obvious, but PSOS will only work when your file is hosted in FileMaker Server 13.
Note: This may be obvious, but PSOS will only work when your file is hosted in FileMaker Server 13+.
DayBack has a script that runs before enabling PSOS which verifies you are running FileMaker Server. In older versions of DayBack, the method we used to check for this did not return True when using FileMaker Cloud. If PSOS is not enabling and your server is on FileMaker Cloud, either update to the latest DayBack, or replace the calculation in the "Can Run On Server" script with the following:
DayBack has a script that runs before enabling PSOS which verifies you are running FileMaker Server. In older versions of DayBack, the method we used to check for this did not return True when using FileMaker Cloud. If PSOS is not enabling and your server is on FileMaker Cloud, either update to the latest DayBack, or apply the specific change as described in this support article.
FileMaker Cloud
DayBack has a script that runs before enabling PSOS which verifies you are running FileMaker Server. In older versions of DayBack, the method we used to check for this did not return True when using FileMaker Cloud. If PSOS is not enabling and your server is on FileMaker Cloud, either update to the latest DayBack, or replace the calculation in the "Can Run On Server" script with the following:
Thus, PSOS is a "switch" in DayBack. You can turn this on from the calendars's settings tab or turn it on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
Thus, PSOS is a "switch" in DayBack. You can turn this on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
Caution
If you've linked or embedded the calendar into your file check that your file's start up script bails out when run on FileMaker Server. Each PSOS script initiated runs the start up script in any required files and that can really slow things down. Feel free to use the same routine used as the first lines of DayBack's "Upon Opening" script:
Note: The PSOS option is included in SeedCode calendar version 7.25 (a paid upgrade from earlier versions). Check out our version history for more.
Why would I want to use PSOS?
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can have the server do a lot of the heavy lifting the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.). You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file.
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times 10-40 times faster when using PSOS on a WAN (your mileage may vary).
Why Would I Want to Use PSOS?
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can have the server do a lot of the heavy lifting the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.). More interestingly, you can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file.
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network).
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. But it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server (when there is a lot of latency in your connection to the server). But it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
Thus, PSOS is a "switch" in the Pro Calendar. You can turn this on from the calendars's settings tab or turn it on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
Adding PSOS to your Calendar file
If you want to add this PSOS functionality into a SeedCode calendar you already have, you can... following these instructions.
First, upgrade to the new calendar. And you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps from that file: then follow these instructions:
1. Import these three custom functions into your file: (yes, that �#� sign is the full name of the first one)
2. Copy/paste the new "Check for FileMaker Server" script into your file.
3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using Select All and Copy/Paste: (NOTE: do not delete the scripts themselves; only the contents)
(NOTE: those last three scripts are unrelated to PSOS, but updating them will fix some minor bugs we found.)
4. You'll also have to edit the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. If you haven't modified any of the settings in this script in your file, then you can just copy/paste the entire contents from the new file into yours (like you did with the other scripts above). However, if you have modified your settings, you'll want to selectively copy/paste these new steps:
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", then rerun the "Upon Opening" script.
That's it, enjoy!
I'm Getting a Notification Dialog saying PSOS isn't available?
We thought developers would like to know about those cases where they'e set the calendar to use PSOS but it won't be used: such as when the calendar is opened shared from FileMaker Pro instead of FileMaker Server.
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
Thus, PSOS is a "switch" in DayBack. You can turn this on from the calendars's settings tab or turn it on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our version history for more.
Note: The PSOS option is included in SeedCode calendar version 7.25 (a paid upgrade from earlier versions). Check out our version history for more.
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times 10-20 times faster when using PSOS on a WAN (your mileage may vary).
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times 10-40 times faster when using PSOS on a WAN (your mileage may vary).
Why wouldn't I want PSOS on all the time?
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. And it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
Why wouldn't everyone want PSOS on?
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. But it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
''Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our version history for more. ''
Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our version history for more.
Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our version history for more.
''Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our version history for more. ''
Why wouldn't I want PSOS on all the time?
The speed improvements in PSOS are most dramatic when you're far away from your FileMaker Server. And it does come with a trade off: scripts run with PSOS don't cache their results the way scripts running locally would. So if your server is close enough, you may not want PSOS running because you'd rather have the caching.
Here is an exaggerated example:
Thus, PSOS is a "switch" in the Pro Calendar. You can turn this on from the calendars's settings tab or turn it on by default by editing the comment for PSOS in the script ""Load Calendar Settings - On Startup --- Edit Configuration Here ---".
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary).
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times 10-20 times faster when using PSOS on a WAN (your mileage may vary).
That's it, enjoy!
That's it, enjoy!
I'm Getting a Notification Dialog saying PSOS isn't available?
We thought developers would like to know about those cases where they'e set the calendar to use PSOS but it won't be used: such as when the calendar is opened shared from FileMaker Pro instead of FileMaker Server.
To get rid of this dialog simply delete the first Show Custom Dialog step in the script "Cast Events as Variables - Build Query" after the comment "Script is running on the server (PSOS)."
Note: The PSOS option will be included in SeedCode's Calendar for Web Direct, which is almost ready. Signup for our newsletter to be the first to know when it's released.
Note: The PSOS option is included in SeedCode calendar version 7.23 and higher. Check out our version history for more.
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (over the internet). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary). You might not see any improvement on a LAN (on the local network).
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (i.e. opening your file from outside your local network). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary).
You'll likely not see any improvement on a LAN (when you're ON the local network).
If you want to add this PSOS functionality into your calendar file, you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps. Ask us for the latest build, then follow these instructions:
If you want to add this PSOS functionality into a SeedCode calendar you already have, you can... following these instructions.
First, upgrade to the new calendar. And you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps from that file: then follow these instructions:
Set Variable [$$sc_PSOS; Value:"No"...]
Set Variable [$$sc_SortEvents; Value:"Yes"...]
If[]
section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", then rerun the "Upon Opening" script.
5. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
Set Variable [$$sc_PSOS; Value:"No"...]
Set Variable [$$sc_SortEvents; Value:"Yes"...]
If[]
section at the end of the script (which contains a few other nested If sections), immediately following the comment "If PSOS is on, make sure PSOS is available."
5. The calendar ships with that new $$sc_PSOS variable mentioned above set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
4. You'll also have to edit the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. If you haven't modified any of the settings in this script in your file, then you can just copy/paste the entire contents from the new file into yours. If you have modified your settings, you'll want to selectively copy/paste these new steps:
4. You'll also have to edit the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. If you haven't modified any of the settings in this script in your file, then you can just copy/paste the entire contents from the new file into yours (like you did with the other scripts above). However, if you have modified your settings, you'll want to selectively copy/paste these new steps:
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
5. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.) to the server. You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can have the server do a lot of the heavy lifting the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.). You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file.
Using PSOS can result in dramatic performance improvements in these types of operations when working over a WAN (over the internet). Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS on a WAN (your mileage may vary). You might not see any improvement on a LAN (on the local network).
4. You'll also have to edit the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. If you haven't modified any of the settings in this script in your file, then you can just copy/paste the entire contents from the new file into yours. If you have modified your settings, you'll want to selectively copy/paste these new steps:
4. ->There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
<4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
4. ->There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
1. Import these three custom functions into your file:
1. Import these three custom functions into your file:
3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using Select All and Copy/Paste:
3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using Select All and Copy/Paste:
<4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with your file being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with yourfile being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
2. Copy/paste the new "Check for FileMaker Server" script into your file.
2. Copy/paste the new "Check for FileMaker Server" script into your file.
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with yourfile being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with yourfile being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
4. There is a new variable called $$sc_PSOS that gets set in the "Load Calendar Settings - On Startup --- Edit Configuration Here ---" script. The calendar ships with this preference set to "No". To start using PSOS (with yourfile being hosted in FileMaker Server 13 and having made all of the modifications outlined above), change the value that is set into the $$sc_PSOS variable to "Yes", the rerun the "Upon Opening" script.
3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using copy/paste:
3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using Select All and Copy/Paste:
2. Copy/paste these five new scripts into your file:
2. Copy/paste the new "Check for FileMaker Server" script into your file.
(NOTE: those last three scripts are unrelated to PSOS, but updating them will fix a couple of minor bugs.)
(NOTE: those last three scripts are unrelated to PSOS, but updating them will fix some minor bugs we found.)
2. Create a new layout named "Calendar - Web Viewer", and associate it with the CalendarInterface table
3. Copy/paste these five new scripts into your file:
2. Copy/paste these five new scripts into your file:
4. Replace the entire contents (all steps) of these eight scripts in your file with the contents of these scripts from the new file using copy/paste:
(note: do not delete the scripts themselves; only the contents)
3. Replace the entire contents (all steps) of these seven scripts in your file with the contents of these scripts from the new file using copy/paste:
(NOTE: do not delete the scripts themselves; only the contents)
(NOTE: those last three scripts are unrelated to PSOS, but updating them will fix a couple of minor bugs.)
1. Import these custom functions into your file:
1. Import these three custom functions into your file:
3. Copy/paste these new scripts into your file:
3. Copy/paste these five new scripts into your file:
4. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:
4. Replace the entire contents (all steps) of these eight scripts in your file with the contents of these scripts from the new file using copy/paste:
2. Create a new layout associated with the CalendarInterface table, named "Calendar - Web Viewer":
2. Create a new layout named "Calendar - Web Viewer", and associate it with the CalendarInterface table
2. Copy/paste these new scripts into your file:
2. Create a new layout associated with the CalendarInterface table, named "Calendar - Web Viewer":
3. Copy/paste these new scripts into your file:
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:
4. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:
If you want to add this PSOS functionality into your calendar file, ask us for the latest build, then follow these instructions:
If you want to add this PSOS functionality into your calendar file, you'll need FileMaker Advanced so you can add custom functions and copy/paste script steps. Ask us for the latest build, then follow these instructions:
Note: This may seem obvious, but PSOS will only work when your file is hosted in FileMaker Server 13.
Note: This may be obvious, but PSOS will only work when your file is hosted in FileMaker Server 13.
Note: This may seem obvious, but we'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.
Note: This may seem obvious, but PSOS will only work when your file is hosted in FileMaker Server 13.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.) to the server. You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.) to the server. You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query on a hosted file. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.) to the server. You can also avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster using PSOS than without it.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster when using PSOS.
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script on the server. That means you can have the server can do a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and you can avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster with PSOS than without it.
The "Perform Script on Server" script step was introduced in FileMaker 13. PSOS lets a client of a hosted file run a sub script on the server. So with some careful planning, you can offload a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Perform Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster using PSOS than without it.
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script on the server. That means you can have the server can do a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and you can avoid having to move large amounts of data over the network, which is what normally happens when a client machine runs a Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster with PSOS than without it.
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script on the server. That means you can have the server can do a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and you can avoid moving large amounts of data over the network, which is what normally happens when the client machine runs a Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster with PSOS than without it.
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script on the server, which means the server does all of the heavy lifting (processing, data manipulation, etc.). This can result in dramatic performance improvements for certain operations. Our tests showed that using PSOS in the Pro Calendar results in refresh times 20-40 times faster than without it.
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script on the server. That means you can have the server can do a lot of the work the client machine would normally have to do (finding, sorting, processing, other data manipulation, etc.), and you can avoid having to move large amounts of data over the network, which is what normally happens when a client machine runs a Find or an SQL query. Using PSOS can result in dramatic performance improvements in these types of operations. Our tests with the Pro Calendar showed refresh times 20-40 times faster with PSOS than without it.
If you want to make these changes in your calendar file, ask us for the latest build, then follow these instructions:
If you want to add this PSOS functionality into your calendar file, ask us for the latest build, then follow these instructions:
If you want to make these changes in your copy of the calendar, ask us for a copy of the latest build, then follow these instructions:
If you want to make these changes in your calendar file, ask us for the latest build, then follow these instructions:
If you want to make these changes in your copy of the calendar, ask us for a copy of the latest build, then follow these instructions:
Note: This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.
Note: This may seem obvious, but we'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script on the server, which means the server does all of the heavy lifting (processing, data manipulation, etc.). This can result in dramatic performance improvements for certain operations. Our tests showed that using PSOS in the Pro Calendar results in refresh times 20-40 time faster than without it. This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script on the server, which means the server does all of the heavy lifting (processing, data manipulation, etc.). This can result in dramatic performance improvements for certain operations. Our tests showed that using PSOS in the Pro Calendar results in refresh times 20-40 times faster than without it.
Note: This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.
Note: The PSOS options will be included in SeedCode's Calendar for Web Direct, which is almost ready. Signup for our newsletter to be the first to know when it's released.
Note: The PSOS option will be included in SeedCode's Calendar for Web Direct, which is almost ready. Signup for our newsletter to be the first to know when it's released.
Why would I want to PSOS?
Why would I want to use PSOS?
Why would I want to PSOS?
The "Perform Script on Server" script step was introduced in FileMaker 13. With some careful planning, PSOS lets a client of a hosted file run a sub script on the server, which means the server does all of the heavy lifting (processing, data manipulation, etc.). This can result in dramatic performance improvements for certain operations. Our tests showed that using PSOS in the Pro Calendar results in refresh times 20-40 time faster than without it. This may seem obvious, but I'll say it anyway: PSOS will only work when your file is hosted in FileMaker Server 13.
1. Import these custom functions into your file (yes, that �#� sign is the full name of the first one):
1. Import these custom functions into your file: (yes, that �#� sign is the full name of the first one)
2. Copy/paste these new scripts into your file:
2. Copy/paste these new scripts into your file:
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste:
1. Import these custom functions into your file (yes, that �#� sign is the full name of the first one):
1. Import these custom functions into your file (yes, that �#� sign is the full name of the first one):
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste: (note: do not delete the scripts themselves; only the contents)
1. Import these custom functions into your file (yes, that �#� sign is the full name of the first one):
1. Import these custom functions into your file (yes, that �#� sign is the full name of the first one):
2. Copy/paste these new scripts into your file:
2. Copy/paste these new scripts into your file:
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
Note: The PSOS options will be included in SeedCode's Calendar for Web Direct, which is almost ready. Signup for our newsletter to be the first to know when it's released.
Perform Script on Server (PSOS)
(:title Perform Script on Server (PSOS):)
Adding PSOS to your Calendar file
First, import these custom functions into your file (yes, that �#� sign is the full name of the first one):
1. Import these custom functions into your file (yes, that �#� sign is the full name of the first one):
Copy/paste these new scripts into your file:
2. Copy/paste these new scripts into your file:
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
3. Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
"#" "#Assign" "#AssignGlobal"
Perform Script on Server (PSOS)
- Assign
- AssignGlobal
"#" "#Assign" "#AssignGlobal"
FileMaker Find FileMaker Find - Apply Filters ( SourceNo ) Check for FileMaker Server Sort FileMaker Records --- Edit Sort Orders Here --- Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents): Insert Events File Into Calendar Cast Events as Variables - Build Query Capture Events by Date Range - Run SQL Query Go to Calendar Layout Upon Opening Clear Event Parsing Variables Click in / Drag Event Load Calendar Graphics
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents):
First, import these custom functions into your file (yes, that �#� sign is the full name of the first one):
- Assign
- AssignGlobal
Copy/paste these new scripts into your file: FileMaker Find FileMaker Find - Apply Filters ( SourceNo ) Check for FileMaker Server Sort FileMaker Records --- Edit Sort Orders Here --- Sort FileMaker Records for Gantt Chart --- Edit Sort Orders Here �
Replace the entire contents (all steps) of these scripts in your file with the contents of these scripts from the new file using copy/paste (note: do not delete the scripts themselves; only the contents): Insert Events File Into Calendar Cast Events as Variables - Build Query Capture Events by Date Range - Run SQL Query Go to Calendar Layout Upon Opening Clear Event Parsing Variables Click in / Drag Event Load Calendar Graphics