Troubleshooting
DayBackForFileMaker.Troubleshooting History
Hide minor edits - Show changes to markup
https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png
https://archive.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png
https://www.seedcode.com/rootimages/stikipad/dayback/launch-ie.png
https://archive.seedcode.com/rootimages/stikipad/dayback/launch-ie.png
FileMaker 19: Changes Required
Claris changed some things in FileMaker 19 that introduced some new issues with DayBack Classic. If you'd like to use your DayBack Classic calendar in FileMaker 19, you'll need to be running build 10.61 or later.
Instructions on getting your calendar updated here: In App Updates
This can also happen if your computer goes to sleep or hibernate while the file is open. DayBack exports files to the FileMaker temporary directory that are used for the calendar, and the connection to the temporary directory is broken when the computer sleeps. To prevent this, you can change your computer's settings to not go to sleep or hibernate. As an alternate workaround, you can close and re-open the file or run the "Upon Opening" script to re-establish the files in the temporary directory.
If you've embedded the calendar or implemented the script updates for build 10.50 using a version of FileMaker earlier than 17, and are now having issues opening DayBack in FileMaker 17+, there's likely a script step that needs updating. Using FileMaker 17+, verify that the "Create folders" option of the "Export Field Contents" step on line 18 of the "Set Temp Path Folder" script is toggled "On". Close and re-open the file, or run the "Upon Opening" script for the changes to take effect.
If you recently applied the script updates for build 10.50, and you used FileMaker Pro 16 or earlier, you'll see a blank web viewer and receive the FMP URL when opening the file with FileMaker 17+. To fix this, open the file in FileMaker 17+ and change the "Create folders" option to "On" in the Export Field Contents step on line 18 of the "Set Temp Path Folder" script.
If the buttons to open the custom button action or additional fields trays are missing from your popover, it's likely that you've applied in-app updates to your instance of DayBack, but haven't applied the required script updates (specifically from build 10.44). When applying in-app updates, make sure you apply all of the required script updates, from the build you're on, to the latest, as detailed in the version history page here.
If the buttons to open the custom button action or additional fields drawers are missing from your popover, it's likely that you've applied in-app updates to your instance of DayBack, but haven't applied the required script updates (specifically from build 10.44). When applying in-app updates, make sure you apply all of the required script updates, from the build you're on, to the latest, as detailed in the version history page here.
Custom Button Action / Additional Fields buttons are missing
If the buttons to open the custom button action or additional fields trays are missing from your popover, it's likely that you've applied in-app updates to your instance of DayBack, but haven't applied the required script updates (specifically from build 10.44). When applying in-app updates, make sure you apply all of the required script updates, from the build you're on, to the latest, as detailed in the version history page here.
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, if the CalendarInterface record is deleted, or if a new record is added to the CalendarInterface table. If the Because of this, you can add a custom menu set with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, if the CalendarInterface record is deleted, or if a new record is added to the CalendarInterface table. To prevent this, you can add a custom menu set with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
- @-ms-viewport{
width:960px; }
- @-ms-viewport{width:960px;}
Windows and high DPI screens
On Windows systems with a smaller screen and a high DPI (resolution), the calendar text and objects may display very small and unreadable. There are a couple of options to address this, some of which are easier than others.
width:960px; }
- }
- IE Security Settings - Your Internet Explorer security settings may be preventing scripts from running in pages. To fix this, you'll want to open the IE settings, go to the Advanced tab, and check the option for "Allow active content to run in files on My Computer" option. Additionally, you could just click the "Restore advanced settings" button to restore everything to default.
- FileMaker Trial Version - If you're running a trial version of FileMaker, this can sometimes be the cause of this error. If this is the cause of the issue, a licensed version of FileMaker should resolve it. Some users have noted that entering the license info into an already installed trial version does not fix this issue, so you'll need to fully uninstall FileMaker, then re-install FileMaker, entering your license details during setup.
- Windows 7 Remote Desktop / Terminal Services users - Some users of Windows 7 through Remote Desktop Services have reported this issue and haven't been able to resolve it with the above two solutions. In this case, unfortunately, the only option is to acknowledge the script warning and allow scripts to run when loading the calendar.
- FileMaker Trial Version - If you're running a trial version of FileMaker, this can sometimes be the cause of this error. If this is the cause of the issue, a licensed version of FileMaker should resolve it.
- FileMaker Trial Version - If you're running a trial version of FileMaker, this can sometimes be the cause of this error. If this is the cause of the issue, a licensed version of FileMaker should resolve it. Some users have noted that entering the license info into an already installed trial version does not fix this issue, so you'll need to fully uninstall FileMaker, then re-install FileMaker, entering your license details during setup.
Yellow script warning when opening calendar in Windows
When opening the calendar layout, you see a yellow bar warning you: "To help protect your security, Internet Explorer has restricted this webpage from running scripts..."
This warning is shown from Internet Explorer to notify you that the page (DayBack) is trying to run scripts (JavaScript) to load the page. You can click this warning and allow scripts to run, but this will only be retained for the current WebViewer session. If the calendar layout is re-loaded, it will again show the warning.
There are 3 possible causes of this warning that we have been able to verify:
- IE Security Settings - Your Internet Explorer security settings may be preventing scripts from running in pages. To fix this, you'll want to open the IE settings, go to the Advanced tab, and check the option for "Allow active content to run in files on My Computer" option. Additionally, you could just click the "Restore advanced settings" button to restore everything to default.
- FileMaker Trial Version - If you're running a trial version of FileMaker, this can sometimes be the cause of this error. If this is the cause of the issue, a licensed version of FileMaker should resolve it.
- Windows 7 Remote Desktop / Terminal Services users - Some users of Windows 7 through Remote Desktop Services have reported this issue and haven't been able to resolve it with the above two solutions. In this case, unfortunately, the only option is to acknowledge the script warning and allow scripts to run when loading the calendar.
Excessive memory use in FileMaker for Windows 16+
There is a reported issue in FileMaker for Windows 16+ with garbage collection when refreshing/reloading WebViewers. This means that every time a WebViewer is refreshed, additional memory is used for the FileMaker process until the program is closed. This usually is not an issue on most computers, but those with limited memory (RAM) may experience performance drops.
Unfortunately, there isn't a fix for this issue, but rather a workaround of closing FileMaker and re-opening your solution.
If you experience this issue and would like to encourage a fix from FileMaker, we encourage you to Give Feedback or view the reported issue.
Lists in FileMaker require that you have at least two items to be considered a value list. In older builds of DayBack, in the $$sc_CustomEventActions variable, we leave an empty string ("") as the second list item to account for this. If you've recently made changes to the custom actions of a source and you only have one custom action, make sure you've left the extra empty list item in there so that the list is complete.
After adding a new source, the calendar won't load
DayBack needs to load sources in numerical order without skipping numbers. So if your "Load Source Settings at Startup" script is set up to only load sources 1 and 3 (for example, you've disabled the sample ToDoList source), then the calendar will not load properly. To resolve this, make sure your active source numbers don't skip numbers. For your new source, you'll likely need to
After adding a new source, the calendar won't load
DayBack needs to load sources in numerical order without skipping numbers. So if your "Load Source Settings at Startup" script is set up to only load sources 1 and 3 (for example, you've disabled the sample ToDoList source), then the calendar will not load properly. To resolve this, make sure your active source numbers don't skip numbers. For your new source, you'll likely need to
I can't zoom on my Windows touchscreen device
Since DayBack is viewed in a web viewer, Windows touchscreen zoom features do not work on the calendar. To zoom, use the Ctrl-Scroll on a mouse.
(:include TouchScreens:)
- "Relationship is missing." Double check to make sure the table occurrence name for your calendar source matches the $$sc_SourceTableOccurrenceName variable set within the "Load Calendar Settings at Startup..." script. The value in that variable may be matching a table occurrence on DayBack's relationship graph -- just not the correct one for this source.
- "Relationship is missing." Double check to make sure the table occurrence name for your calendar source matches the $$sc_SourceTableOccurrenceName variable set within the "Load Source Settings at Startup..." script. The value in that variable may be matching a table occurrence on DayBack's relationship graph -- just not the correct one for this source.
The calendar uses the fmp url protocol to call scripts in your file. Some computers can get confused as to which copy of FileMaker to use in responding to these url calls. Symptoms can include the calendar showing now events, or launching another copy of FileMaker on startup.
The calendar uses the fmp url protocol to call scripts in your file. Some computers can get confused as to which copy of FileMaker to use in responding to these url calls. Symptoms can include the calendar showing no events, or launching another copy of FileMaker on startup.
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker 16. Learn more here: FMP URLs in Next.
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker 16. Learn more here: FMP URLs.
Losing custom translations or CSS themes
FileMaker "next": Changes Required
If you're seeing this error when you first open DayBack in FileMaker "Next"...
FileMaker 16: Changes Required
If you're seeing this error when you first open DayBack in FileMaker 16...
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker Next. Learn more here: FMP URLs in Next.
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker 16. Learn more here: FMP URLs in Next.
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker Next. Learn more here: FMP URLs in FM16.
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker Next. Learn more here: FMP URLs in Next.
If you're seeing this error when you first open DayBack in FileMaker 16...
If you're seeing this error when you first open DayBack in FileMaker "Next"...
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker 16. Learn more here: FMP URLs in FM16.
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker Next. Learn more here: FMP URLs in FM16.
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, or if the CalendarInterface record is deleted. Because of this, you can add a custom menu set with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, if the CalendarInterface record is deleted, or if a new record is added to the CalendarInterface table. If the Because of this, you can add a custom menu set with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
Setting selections aren't retained when leaving the calendar on Windows"
On windows FileMaker does not retain cookies or local storage items in the web viewer. This is a limitation that is present when Internet Explorer is not open. If Internet Explorer is open while using DayBack on windows then cookies are available and can be used to store settings for that session.
We have created a simple command for determining if Internet Explorer is not open, if it is then IE will be launched hidden. To add this behavior to your file follow the directions below:
Setting selections aren't retained when leaving the calendar on Windows
On windows FileMaker does not retain cookies or local storage items in the webviewer. This is a limitation that is present when Internet Explorer is not open. If Internet Explorer is open while using DayBack on windows then cookies are available and can be used to store settings for that session.
We have created a simple command for determining if Internet Explorer is not open, if it is not open then IE will be launched hidden. To add this behavior to your file follow the directions below:
cmd.exe /c tasklist | find "iexplore.exe" || start /B /MIN iexplore.exe
- cmd.exe /c tasklist | find "iexplore.exe" || start /B /MIN iexplore.exe
Then you can choose to either run this script at startup or as a script trigger on layout exit. Startup is great is then it only runs once, the issue with relying on that is that if a user closes IE during the use of the calendar saving settings for the session will no longer work. So we recommend a combination. Run the script on startup to make sure IE is open. Then add a script trigger to the "Calendar" layout to run the script for "OnLayoutExit". To ensure IE has time to fully launch please add a "Pause/Resume" script step for 2 seconds at the end of the "Launch IE" script.
Wrap the send event script step in an if statement so we only run this command in Windows. The if statement will evaluate:
- Abs ( Get ( SystemPlatform ) ) = 2
Then you can choose to either run this script at startup or as a script trigger "OnLayoutExit". Running on startup is great as then it only runs once, be aware that if a user closes IE during the use of the calendar saving settings for the session will no longer work. So we recommend a combination. Run the script on startup to make sure IE is open. Then add a script trigger to the "Calendar" layout to run the script for "OnLayoutExit". To ensure IE has time to fully launch please add a "Pause/Resume" script step for 2 seconds at the end of the "Launch IE" script inside the if statement as shown in the image above.
There is a script step at the beginning of DayBack's "Upon Opening" script (at line 18) that records the current window name being used for the calendar: it sounds like you've renamed the window *after* that script ran. Just return there and use the Upon Opening script to set the window name you want to use (at line 15) and you should be all set.
There is a script step at the beginning of DayBack's "Upon Opening" script (at line 18) that records the current window name being used for the calendar: it sounds like you've renamed the window *after* that script ran. Just return there and use the Upon Opening script to set the window name you want to use (at line 15) and you should be all set.
Setting selections aren't retained when leaving the calendar on Windows"
On windows FileMaker does not retain cookies or local storage items in the web viewer. This is a limitation that is present when Internet Explorer is not open. If Internet Explorer is open while using DayBack on windows then cookies are available and can be used to store settings for that session.
We have created a simple command for determining if Internet Explorer is not open, if it is then IE will be launched hidden. To add this behavior to your file follow the directions below:
Create a new script called "Launch IE"
In this new script add a "Send Event" script step, and select the "text" option. Then paste the code below in the text box:
cmd.exe /c tasklist | find "iexplore.exe" || start /B /MIN iexplore.exe
It should look like this: https://www.seedcode.com/rootimages/stikipad/dayback/launch-ie.png
Then you can choose to either run this script at startup or as a script trigger on layout exit. Startup is great is then it only runs once, the issue with relying on that is that if a user closes IE during the use of the calendar saving settings for the session will no longer work. So we recommend a combination. Run the script on startup to make sure IE is open. Then add a script trigger to the "Calendar" layout to run the script for "OnLayoutExit". To ensure IE has time to fully launch please add a "Pause/Resume" script step for 2 seconds at the end of the "Launch IE" script.
Here is a test to make sure the URL protocol is working properly in your version, along with instructions on hot to fox it: FMP URLs
Here is a test to make sure the URL protocol is working properly in your version, along with instructions on how to fix it: FMP URLs
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker 16. Learn more here: FMP URLs in FM16?.
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker 16. Learn more here: FMP URLs in FM16.
FileMaker "next": Changes Required
Test of hiding content
FileMaker 16: Changes Required
If you're seeing this error when you first open DayBack in FileMaker 16...
https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png
...you'll need to a make a simple change in your solution to accommodate a new feature in FileMaker 16. Learn more here: FMP URLs in FM16?.
The calendar uses the fmp url protocol to call scripts in your file. Some computers can get confused as to which copy of FileMaker to use in responding to these url calls.
You can verify that your fmp url calls are working correctly by opening DayBack, then clicking on following link: fmp://$/DayBack.fmp12?script=Unused¶m=run
If you receive a popup in FileMaker with the message "This button is not yet assigned to anything", your fmp url calls are working correctly.
If the above test fails to run, or gives you a different error message, your fmp url calls are not functioning properly. Fortunately this is pretty easy to fix...
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX.
- 1. Open Regedit and Backup your registry. (Instructions Here)
- 2. Find the following key:
HKEY_CLASSES_ROOT\FMP\shell\open\command
- 3. Modify the "(Default)" value with the path to the version of FileMaker you'd like to use by default with the following added at the end: %1. for example:
C:\Program Files\FileMaker\FileMaker Pro 15 Advanced\FileMaker Pro Advanced.exe %1
The calendar uses the fmp url protocol to call scripts in your file. Some computers can get confused as to which copy of FileMaker to use in responding to these url calls. Symptoms can include the calendar showing now events, or launching another copy of FileMaker on startup.
Here is a test to make sure the URL protocol is working properly in your version, along with instructions on hot to fox it: FMP URLs
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can't locate this file the preference pane mentioned above is the way to go.
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX.
If the above test fails to run, or gives you a different error message, your fmp url calls are not functioning properly. Fortunately this is pretty easy to fix.
If the above test fails to run, or gives you a different error message, your fmp url calls are not functioning properly. Fortunately this is pretty easy to fix...
The calendar uses the fmp url protocol to call scripts in your file. Some folks computers can get confused as to which copy of FileMaker to use in responding to these url calls.
The calendar uses the fmp url protocol to call scripts in your file. Some computers can get confused as to which copy of FileMaker to use in responding to these url calls.
Url Issues, or the Calendar Seems to be Opening an Older Copy of FileMaker
URL Issues, or the Calendar Seems to be Opening an Older Copy of FileMaker
The Calendar Seems to be Opening an Older Copy of FileMaker
Url Issues, or the Calendar Seems to be Opening an Older Copy of FileMaker
The calendar uses the fmp:/url protocol to call scripts in your file. Some folks computers can get confused as to which copy of FileMaker to use in responding to these url calls. Fortunately this is pretty easy to fix.
The calendar uses the fmp url protocol to call scripts in your file. Some folks computers can get confused as to which copy of FileMaker to use in responding to these url calls.
You can verify that your fmp url calls are working correctly by opening DayBack, then clicking on following link: fmp://$/DayBack.fmp12?script=Unused¶m=run
If you receive a popup in FileMaker with the message "This button is not yet assigned to anything", your fmp url calls are working correctly.
If the above test fails to run, or gives you a different error message, your fmp url calls are not functioning properly. Fortunately this is pretty easy to fix.
There is a script step at the beginning of DayBack's "Upon Opening" script (at line 18) that records the current window name being used for the calendar: it sounds like you've renamed the window *after* that script ran. Just return there and use the Upon Opening script to rename the window (at line 15) and you should be all set.
There is a script step at the beginning of DayBack's "Upon Opening" script (at line 18) that records the current window name being used for the calendar: it sounds like you've renamed the window *after* that script ran. Just return there and use the Upon Opening script to set the window name you want to use (at line 15) and you should be all set.
In some versions of Windows, parts of your event detail window (when not using DayBack's event popover) can appear to hang over the calendar after closing it. To resolve this, add two "Move/Resize Window" script steps to the bottom of the "Close Event Window & Refresh Calendar" script. Have the first set the width to Get ( WindowWidth ) + 1, and the second set the width to Get ( WindowWidth ) - 1. Users should not notice these adjustments, but the calendar will redraw so that the event window is fully cleared away!
In some versions of Windows, parts of your event detail window (when not using DayBack's event popover) can appear to hang over the calendar after closing it. To resolve this, add two "Move/Resize Window" script steps to the bottom of the "Close Event Window & Refresh Calendar" script. Have the first set the width to Get ( WindowWidth ) + 1, and the second set the width to Get ( WindowWidth ) - 1. Users should not notice these adjustments, but the calendar will redraw so that the event window is fully cleared away!
I'm seeing "The calendar is meant to run in the main solution window only"
This warning is meant to fire if you try to make a second calendar window, but can also come up if you're renaming the calendar window after DayBack's Upon Opening script has run.
There is a script step at the beginning of DayBack's "Upon Opening" script (at line 18) that records the current window name being used for the calendar: it sounds like you've renamed the window *after* that script ran. Just return there and use the Upon Opening script to rename the window (at line 15) and you should be all set.
- 1. Open Regedit and Backup your registry. (Instructions Here)
- 2. Find the following key:
HKEY_CLASSES_ROOT\FMP\shell\open\command
- 3. Modify the "(Default)" value with the path to the version of FileMaker you'd like to use by default with the following added at the end: %1. for example:
C:\Program Files\FileMaker\FileMaker Pro 15 Advanced\FileMaker Pro Advanced.exe %1
What's Wrong?
If you can't see any events in the calendar after your integration, here are a couple things to check.
No events appearing on the calendar?
If you can't see any events in the calendar after your integration, here are a few things to check.
No events appearing on the calendar
If your file is set up to auto-enter an account that does not have access to the event data, and it is being hosted in FileMaker Server, and you are using PSOS, your users might not see any data on the DayBack UI. This is because when scripts run on the server they use the auto-login account to query the events table. The solution is to add a "Re-Login" step in your OnFirstWindowOpen script so PSOS will always use the Admin account. Wrap this in an If[] condition with the following formula:
Rarely, some months may appear to have all events missing, caused by a lone backslash "\" in one of your event records. If an event field ends in or contains only a backslash, removing this character or adding another character after it will correct the issue.
In some versions of Windows, parts of your event detail window (when not using DayBack's event popover) can appear to hang over the calendar after closing it. To resolve this, add two "Move/Resize Window" script steps to the bottom of the "Close Event Window & Refresh Calendar" script. Have the first set the width to Get ( WindowWidth ) + 1, and the second set the width to Get ( WindowWidth ) - 1. Users should not notice these adjustments, but the calendar will redraw so that the event window is fully cleared away!
In some versions of Windows, parts of your event detail window (when not using DayBack's event popover) can appear to hang over the calendar after closing it. To resolve this, add two "Move/Resize Window" script steps to the bottom of the "Close Event Window & Refresh Calendar" script. Have the first set the width to Get ( WindowWidth ) + 1, and the second set the width to Get ( WindowWidth ) - 1. Users should not notice these adjustments, but the calendar will redraw so that the event window is fully cleared away!
Losing custom translations or CSS themes
Losing custom translations or CSS themes
I'm seeing "Host Capacity is Exceeded" warnings
I'm seeing "Host Capacity is Exceeded" warnings
After adding a new source, the calendar won't load
DayBack needs to load sources in numerical order without skipping numbers. So if your "Load Source Settings at Startup" script is set up to only load sources 1 and 3 (for example, you've disabled the sample ToDoList source), then the calendar will not load properly. To resolve this, make sure your active source numbers don't skip numbers. For your new source, you'll likely need to
In some versions of Windows, parts of your event detail window (when not using DayBack's event popover) can appear to hang over the calendar after closing it. To resolve it, add two "Move/Resize Window" script steps to the bottom of the "Close Event Window & Refresh Calendar" script. Have the first set the width to Get ( WindowWidth ) + 1, and the second set the width to Get ( WindowWidth ) - 1. The user should not notice these adjustments, but the calendar should redraw so that the event window is fully cleared away.
In some versions of Windows, parts of your event detail window (when not using DayBack's event popover) can appear to hang over the calendar after closing it. To resolve this, add two "Move/Resize Window" script steps to the bottom of the "Close Event Window & Refresh Calendar" script. Have the first set the width to Get ( WindowWidth ) + 1, and the second set the width to Get ( WindowWidth ) - 1. Users should not notice these adjustments, but the calendar will redraw so that the event window is fully cleared away!
If you see a FileMaker warning that the "Host Capacity is Exceeded" when loading the calendar, and DayBack is hosted on a FileMaker Server, it's possible your Server's scripting engine has stopped. To quickly get past this issue, you can disable DayBack's use of PSOS by editing the first Set Variable step in the "Load Calendar Settings - On Startup..." script. You can also restart your server's "fmse" component using the command line on the host machine to get the scripting engine running again and continue taking advantage of PSOS in DayBack.
If you see a FileMaker warning that the "Host Capacity is Exceeded" when loading the calendar, and DayBack is hosted on a FileMaker Server, it's possible your Server's scripting engine has stopped. To quickly get past this issue, you can disable DayBack's use of PSOS by editing the first Set Variable step in the "Load Calendar Settings - On Startup..." script. You can also restart your server's "fmse" component using the command line on the host machine to get the scripting engine running again and continue taking advantage of PSOS in DayBack.
The Event Detail window hangs after it's closed
In some versions of Windows, parts of your event detail window (when not using DayBack's event popover) can appear to hang over the calendar after closing it. To resolve it, add two "Move/Resize Window" script steps to the bottom of the "Close Event Window & Refresh Calendar" script. Have the first set the width to Get ( WindowWidth ) + 1, and the second set the width to Get ( WindowWidth ) - 1. The user should not notice these adjustments, but the calendar should redraw so that the event window is fully cleared away.
If you see "Summarizing Field "DBk_WebViewerEventData" it could be because you're returning a TON of data from FileMaker. You'll find more about this and strategies to slim down your event payload as the last section on the page here: Speed.
If you see "Summarizing Field "DBk_WebViewerEventData" it could be because you're returning a TON of data from FileMaker. You'll find more about this and strategies to slim down your event payload as the last section on the page here: Speed.
I'm seeing "Host Capacity is Exceeded" warnings
If you see a FileMaker warning that the "Host Capacity is Exceeded" when loading the calendar, and DayBack is hosted on a FileMaker Server, it's possible your Server's scripting engine has stopped. To quickly get past this issue, you can disable DayBack's use of PSOS by editing the first Set Variable step in the "Load Calendar Settings - On Startup..." script. You can also restart your server's "fmse" component using the command line on the host machine to get the scripting engine running again and continue taking advantage of PSOS in DayBack.
If you see "Summarizing Field "DBk_WebViewerEventData" it could be because you're returning a TON of data from FileMaker. You'll find more about the and strategies to slim down your event payload as the last section on the page here: Speed.
If you see "Summarizing Field "DBk_WebViewerEventData" it could be because you're returning a TON of data from FileMaker. You'll find more about this and strategies to slim down your event payload as the last section on the page here: Speed.
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, or if the CalendarInterface record is deleted. Because of this, you can add a custom menu set with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, or if the CalendarInterface record is deleted. Because of this, you can add a custom menu set with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
I'm seeing "Summarizing..." when the calendar loads
If you see "Summarizing Field "DBk_WebViewerEventData" it could be because you're returning a TON of data from FileMaker. You'll find more about the and strategies to slim down your event payload as the last section on the page here: Speed.
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, or if the CalendarInterface record is deleted. Because of this, you can add a custom menu with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, or if the CalendarInterface record is deleted. Because of this, you can add a custom menu set with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
I seem to be losing my custom translations or CSS themes!
Losing custom translations or CSS themes
There are a couple of fields you need to add to your contact and project tables and it can be easy to overlook these--or the fields may be there but be commented out (that is, they may begin with /* and end with */). The fields are described here, please take a moment to make sure they're in your contact or project table and that they're returning data (ie add the fields to a layout and look at the fields in browse mode). If they're not returning data it's likely that the calcs are commented out: uncomment them and follow the instructions inside each calc to point it at the correct fields in your contact or project.
There are a couple of fields you need to add to your contact and project tables and it can be easy to overlook these--or the fields may be there but be commented out (that is, they may begin with /* and end with */). The fields are described here, please take a moment to make sure they're in your contact or project table and that they're returning data (ie add the fields to a layout and look at the fields in browse mode). If they're not returning data it's likely that the calcs are commented out: uncomment them and follow the instructions inside each calc to point it at the correct fields in your contact or project.
I seem to be losing my custom translations or CSS themes!
Your custom themes and translations can be overwritten if a "Restore" button is pressed from the "Under the Hood" layout, or if the CalendarInterface record is deleted. Because of this, you can add a custom menu with the "Records" menu removed, and apply it to the layouts based on the CalendarInterface table occurrence. This should prevent the CalendarInterface record from being unintentionally deleted. Also, save the text of your modified theme or translations in a text file outside of FileMaker for backup. That way, you can quickly restore your custom themes or translations in case they are overwritten by pasting them back into DayBack.
Rarely, some months may appear to have all events missing, caused by a lone backslash "\" in one of your event records. If an event field ends in or contains only a backslash, remove this character or add another character after it.
Rarely, some months may appear to have all events missing, caused by a lone backslash "\" in one of your event records. If an event field ends in or contains only a backslash, removing this character or adding another character after it will correct the issue.
Rarely, some months may appear to have all events missing, caused by a lone backslash "\" in one of your event records. If an event field ends in or contains only a backslash, remove this character or add another character after it.
PatternCount (Get(ApplicationVersion); "Server")
Can't link contacts or projects
There are a couple of fields you need to add to your contact and project tables and it can be easy to overlook these--or the fields may be there but be commented out (that is, they may begin with /* and end with */). The fields are described here, please take a moment to make sure they're in your contact or project table and that they're returning data (ie add the fields to a layout and look at the fields in browse mode). If they're not returning data it's likely that the calcs are commented out: uncomment them and follow the instructions inside each calc to point it at the correct fields in your contact or project.
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
- "Field Can't Be Modified." Make sure that all of the fields you mapped on the "Source No 1" layout are writable; that is, not calculation fields. If you are using a calc field for any of those fields, try changing it to a Text field, then set it up to auto-enter a calculated value instead.
- "Field Can't Be Modified." Make sure that all of the fields you mapped on the "Source No 1" layout are writable; that is, not calculation fields. If you are using a calc field for any of those fields, try changing it to a Text field, then set it up to auto-enter a calculated value instead. (The most common cause of 201 errors is mapping a calculated field to the event Summary. You'll want to make sure the field mapped there is editable.)
If you've integrated DayBack 9.42 or earlier into your hosted solution, the problem may be due to the "global" storage setting on the "BuildNumberCalc" calculation field in the CalendarInterface table. Fortunately the fix is easy; simply remove the global storage option on that field.
If you've integrated DayBack 9.42 or earlier into your hosted solution, the problem may be due to the "global" storage setting on the "BuildNumberCalc" calculation field in the CalendarInterface table. Fortunately the fix is easy; simply remove the global storage option on that field.
No events appearing on the calendar
If your file is set up to auto-enter an account that does not have access to the event data, and it is being hosted in FileMaker Server, and you are using PSOS, your users might not see any data on the DayBack UI. This is because when scripts run on the server they use the auto-login account to query the events table. The solution is to add a "Re-Login" step in your OnFirstWindowOpen script so PSOS will always use the Admin account. Wrap this in an If[] condition with the following formula:
PatternCount (Get(ApplicationVersion); "Server")
If you've integrated DayBack 9.42 or earlier into your hosted solution, the problem may be due to the "global" storage setting on the "BuildNumberCalc" calculation field in the CalendarInterface table. That causes a problem when DayBack is deployed within a hosted solution. Remove the global storage option on that field to fix the problem.
If you've integrated DayBack 9.42 or earlier into your hosted solution, the problem may be due to the "global" storage setting on the "BuildNumberCalc" calculation field in the CalendarInterface table. Fortunately the fix is easy; simply remove the global storage option on that field.
- "Field Can't Be Modified." Make sure that all of the fields you mapped on the "Source No 1" layout are writable; that is, not calculation fields. If you are using a calc field for any of those fields, try changing it to a Text field, then set it up to auto-enter a calculated value instead.
- "Field Can't Be Modified." Make sure that all of the fields you mapped on the "Source No 1" layout are writable; that is, not calculation fields. If you are using a calc field for any of those fields, try changing it to a Text field, then set it up to auto-enter a calculated value instead.
Calendar not loading
If you've integrated DayBack 9.42 or earlier into your hosted solution, the problem may be due to the "global" storage setting on the "BuildNumberCalc" calculation field in the CalendarInterface table. That causes a problem when DayBack is deployed within a hosted solution. Remove the global storage option on that field to fix the problem.
- 9. Try changing the BuildNumberCalc field in the CalendarInterface table from a global to an unstored calculation. This can help if you've integrated DayBack into your own file while your file was hosted in FileMaker Server.
- 9. Try changing the BuildNumberCalc field in the CalendarInterface table from a global to an unstored calculation. This can help if you've integrated DayBack into your own file while your file was hosted in FileMaker Server.
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can locate this file the preference pane mentioned above is the way to go.
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can't locate this file the preference pane mentioned above is the way to go.
https://www.seedcode.com/rootimages/stikipad/dayback/fmp-url-pref-pane.png
link
Open ~/Library/Preferences/com.apple.LaunchServices.plist
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13
Attach:rootimages/stikipad/dayback/fmp-url-pref-pane.png Δ Δ
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX so if you can locate this file the preference pane mentioned above is the way to go.
link
Open ~/Library/Preferences/com.apple.LaunchServices.plist \\
Errors when Editing Events
Some tips for errors you might see when dragging events around or editing them...
The Calendar Seems to be Opening an Old Copy of FileMaker
The Calendar Seems to be Opening an Older Copy of FileMaker
What's wrong?
What's Wrong?
My startup script keeps deleting and re-creating the calendar interface records, is this normal?
No. But it isn't lethal either. Here is how to fix it.
As you probably know, the calendar requires some dummy records in a table called CalendarRows. Our script " Load Calendar Settings - On Startup --- Edit Configuration Here ---" tries to make sure that users haven't deleted, duplicated, or created new records in this table.
I imagine the reason it is deleting and creating them each time you launch is that the script is no longer running from a layout were it can evaluate "CalendarRows::RowNumber". If you change the beginning of the script to go to a layout based on CalendarInterface (where our home layout is / used to be) the script should only reset the CalendarRows table if there is a problem.
Just don't go to one of the actual calendar layouts just to get to a layout based on CalendarInterface, since those layout are script triggered and could delay / loop your startup.
Events are appearing in the wrong place
This is usually caused by carriage returns or other uncommon characters in your data. The most common cause is a trailing carriage return in one of the fields used in your zscEventSummaryCalc field (most likely the Summary or Description field), or ANY carriage return in your Status field (the calendar does not support multiple values in the Status field).
and you'll find an array called LSHandlers and a sub-array LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13
The Calendar Seems to be Opening an Old Copy of FileMaker
The calendar uses the fmp:/url protocol to call scripts in your file. Some folks computers can get confused as to which copy of FileMaker to use in responding to these url calls. Fortunately this is pretty easy to fix.
and you'll find an array called LSHandlers and a sub-array LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13
Just don't go to one of the actual calendar layouts just to get to a layout based on CalendarInterface, since those layout are script triggered and could delay / loop your startup.
Just don't go to one of the actual calendar layouts just to get to a layout based on CalendarInterface, since those layout are script triggered and could delay / loop your startup.
Events are appearing in the wrong place
This is usually caused by carriage returns or other uncommon characters in your data. The most common cause is a trailing carriage return in one of the fields used in your zscEventSummaryCalc field (most likely the Summary or Description field), or ANY carriage return in your Status field (the calendar does not support multiple values in the Status field).