FMP URLs
DayBackForFileMaker.FMPURL History
Hide minor edits - Show changes to output
Changed line 29 from:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png | https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png]]
to:
%center% %newwin width=440px% [[https://archive.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png | https://archive.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png]]
Changed lines 73-74 from:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/RCDefaultApps.png | https://www.seedcode.com/rootimages/stikipad/dayback/RCDefaultApps.png]]
to:
%center% %newwin width=440px% [[https://archive.seedcode.com/rootimages/stikipad/dayback/RCDefaultApps.png | https://archive.seedcode.com/rootimages/stikipad/dayback/RCDefaultApps.png]]
Changed line 77 from:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/RCDefaultURL.png | https://www.seedcode.com/rootimages/stikipad/dayback/RCDefaultURL.png]]
to:
%center% %newwin width=440px% [[https://archive.seedcode.com/rootimages/stikipad/dayback/RCDefaultURL.png | https://archive.seedcode.com/rootimages/stikipad/dayback/RCDefaultURL.png]]
February 25, 2021, at 04:17 PM
by - Updated Mac suggestion to SwiftDefaultApp, since RC Default App is no longer distributed
Changed lines 67-69 from:
-> '''Mac.''' For Mac we recommend using a free 3rd party tool called RCDefaultApp. Wim Decorte, from Soliant, recommended this tool and it does the trick. It can be downloaded here:
->http://www.rubicode.com/Software/RCDefaultApp/
->
to:
-> '''Mac.''' For Mac we recommend using a free 3rd party tool called SwiftDefaultApp. Soliant [[https://www.soliantconsulting.com/blog/filemaker-blog/swiftdefaultapps-rcdefaultapp-catalina/ | recommended this tool]] and it does the trick. It can be downloaded here:
-> https://github.com/Lord-Kamina/SwiftDefaultApps/releases
-> https://github.com/Lord-Kamina/SwiftDefaultApps/releases
January 12, 2021, at 04:08 PM
by - Added links to in-app updates and version history
Added lines 12-15:
Instructions on applying in-app updates can be [[InAppUpdates |found here]].
See changes in the [[VersionHistory | version history page here]].
January 12, 2021, at 03:58 PM
by - Added FM19 section
Added lines 8-11:
!!FileMaker 19: Changes to the FMP URL protocol require updating DayBack
Claris changed some things in FileMaker 19 that caused some issues with DayBack Classic in 19, so we released some updates to address those issues. If you'd like to use your DayBack Classic calendar in FileMaker 19, you'll need to get it updated to the latest build, 10.61.
November 25, 2019, at 09:01 PM
by - typo fix
Changed line 11 from:
FileMaker 18 introduces version-specific URLs like fmp18:// and if you frequently use more than one version of FileMaker, you may want to change your older copy of DayBack to use this new format. Here's how to make taht change: %newwin% [[https://www.seedcode.com/filemaker-18-fmp-urls/ | FileMaker 18 and FMP URLs]].
to:
FileMaker 18 introduces version-specific URLs like fmp18:// and if you frequently use more than one version of FileMaker, you may want to change your older copy of DayBack to use this new format. Here's how to make that change: %newwin% [[https://www.seedcode.com/filemaker-18-fmp-urls/ | FileMaker 18 and FMP URLs]].
September 04, 2019, at 09:55 PM
by - Rewording
Deleted lines 37-38:
Changed lines 40-41 from:
You may see a URL error message in Dayback even if you have enabled FMPurl privileges for your account and sorted out any issues with multiple versions of Filemaker trying to run the urls. If you are experiencing behavior in DayBack where the events will load *and* you are receiving an error message that the FMPurl was not successful, it is likely that the web viewer is not loading the Event data fast enough to both request the data and successfully verify that the FMPurls are working correctly.
to:
You may see a URL error message in Dayback even if you have enabled FMP URL privileges for your account and sorted out any issues with multiple versions of Filemaker. If you are experiencing behavior in DayBack where the events will load *and* you are receiving an error message that the FMPurl was not successful, it is likely that the web viewer is not loading fast enough to report to FileMaker that the FMP URL protocol is working.
Added lines 43-45:
[[#Testing]]
September 04, 2019, at 09:09 PM
by - added section on fmp url OnTimer step might need to be updated if you have events but get URL error
Added lines 39-44:
!!URL Error: Events Showing on Calendar, but Still Getting URL error?
You may see a URL error message in Dayback even if you have enabled FMPurl privileges for your account and sorted out any issues with multiple versions of Filemaker trying to run the urls. If you are experiencing behavior in DayBack where the events will load *and* you are receiving an error message that the FMPurl was not successful, it is likely that the web viewer is not loading the Event data fast enough to both request the data and successfully verify that the FMPurls are working correctly.
To fix this, navigate to the "Check for FMP URL" script, and update the interval of the OnTimer script step starting on line 25. You may want to extend it from 5 seconds to 10 seconds or longer, depending on the processing power of your machine. This will give the script enough of a margin to make sure everything is in its right place when the events are loaded.
Changed lines 9-10 from:
!!FileMaker 17: Changes Required??
to:
!!FileMaker 18: No changes required, but a new opportunity with FMP URLs
FileMaker 18 introduces version-specific URLs like fmp18:// and if you frequently use more than one version of FileMaker, you may want to change your older copy of DayBack to use this new format. Here's how to make taht change: %newwin% [[https://www.seedcode.com/filemaker-18-fmp-urls/ | FileMaker 18 and FMP URLs]].
!!FileMaker 17: Changes Required?
FileMaker 18 introduces version-specific URLs like fmp18:// and if you frequently use more than one version of FileMaker, you may want to change your older copy of DayBack to use this new format. Here's how to make taht change: %newwin% [[https://www.seedcode.com/filemaker-18-fmp-urls/ | FileMaker 18 and FMP URLs]].
!!FileMaker 17: Changes Required?
Changed line 17 from:
!!FileMaker 16+ : Changes Required??
to:
!!FileMaker 16+ : Changes Required?
Changed line 5 from:
This is a special url, prefixed with fmp, that is answered by FileMaker Pro (or Go) instead of by your browser. These URLs can contain scripts and script parameters and it is by opening URLs like this that %newwin% [[https://www.seedcode.com/filemaker-calendar/ | DayBack Calendar]] can talk to FileMaker Pro.
to:
This is a special url, prefixed with fmp, that is answered by FileMaker Pro (or Go) instead of by your browser. These URLs can contain scripts and script parameters and it is by opening URLs like this that webviewer apps like %newwin% [[https://www.seedcode.com/filemaker-calendar/ | DayBack Calendar]] can talk to the FileMaker file they're inside of.
Added lines 46-47:
-> '''Mac & Windows.''' If you're not using your older version of FileMaker, simply uninstall it. This often fixes this. If that isn't an option for you, or doesn't work, one ofthe options below will work:
Changed line 62 from:
-> '''Windows.''' If you've installed multiple instances of FileMaker, URL links will open, by default, in the last version of FileMaker installed. If you'd like to change the default FileMaker version that is used for FMP URL links in Windows, you can modify a registry key, rather than uninstall/re-install that version of FileMaker.
to:
-> '''Windows.''' If you'd like to change the default FileMaker version that is used for FMP URL links in Windows, you can modify a registry key, rather than uninstall/re-install that version of FileMaker.
Added lines 8-11:
!!FileMaker 17: Changes Required??
We’re seeing issues with FileMaker 17 not updating the operating system's FMP URL to point version 17 if a previous version of FileMaker is still installed. For example, if you have 16 still installed, the FMP URL may still work there, but not in 17. Unfortunately, the FMP URL can only work in one version of FileMaker at a time. If you encounter this, scroll down to the Testing & Fixing the FMP URL Protocol section where we have instructions for explicitly setting which version the FMP URL should target.
Changed line 9 from:
!!FileMaker 16: Changes Required??
to:
!!FileMaker 16+ : Changes Required??
Changed line 58 from:
-> First, while this change should not affect your system in a devastating way, if you don't implement it correctly or modify/delete the wrong keys, you make render your system unusable. Therefore, a warning from Microsoft: ''Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.''
to:
-> First, while this change should not affect your system in a devastating way, if you don't implement it correctly or modify/delete the wrong keys, you may render your system unusable. Therefore, a warning from Microsoft: ''Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.''
Added lines 48-49:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/RCDefaultApps.png | https://www.seedcode.com/rootimages/stikipad/dayback/RCDefaultApps.png]]
Added lines 51-52:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/RCDefaultURL.png | https://www.seedcode.com/rootimages/stikipad/dayback/RCDefaultURL.png]]
Changed lines 40-43 from:
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...
-> '''Mac.''' Usually the Mac will open the URL in the highest currently open version of FileMaker. So all you may need to do is quit the version of FileMaker you don' want to be using. But you may be able to modify the launch services plist file directly. 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. This doesn't appear to be in the same place for every version of MacOSX.
-> '''Mac.''' Usually the Mac will open the URL in
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
to:
If the above test fails to run, or gives you a different error message, your fmp url calls are not functioning properly. Unfortunately, The fmp url can only be directed to one version of FileMaker at a time, so the most likely reason for the error is that it's pointed at a different version you are currently using. Fortunately there is a fix to redirect the fmp to the correct version of FileMaker:
-> '''Mac.''' For Mac we recommend using a free 3rd party tool called RCDefaultApp. Wim Decorte, from Soliant, recommended this tool and it does the trick. It can be downloaded here:
-> http://www.rubicode.com/Software/RCDefaultApp/
-> Once you've installed the app, you can open it from your System Preferences, and then go to the Apps tab and make sure the version of FileMaker you want to use the FMP URL has it checked like this:
-> Then go to the URLs tab and direct the fmp url to the version of FileMaker you want to use it like this:
-> and you should be all set.
-> '''Mac.''' For Mac we recommend using a free 3rd party tool called RCDefaultApp. Wim Decorte, from Soliant, recommended this tool and it does the trick. It can be downloaded here:
-> http://www.rubicode.com/Software/RCDefaultApp/
-> Once you've installed the app, you can open it from your System Preferences, and then go to the Apps tab and make sure the version of FileMaker you want to use the FMP URL has it checked like this:
-> Then go to the URLs tab and direct the fmp url to the version of FileMaker you want to use it like this:
-> and you should be all set.
Changed line 13 from:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png | https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png]]
to:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png | https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png]]
Changed line 9 from:
!!FIleMaker 16: Changes Required??
to:
!!FileMaker 16: Changes Required??
Changed lines 9-11 from:
!!FIleMaker 16: Changes Required
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. The first time you open %newwin% [[https://www.seedcode.com/filemaker-calendar/ | DayBack]], ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. The first time you open %newwin% [[https://www.seedcode.com/filemaker-calendar/ | DayBack]], ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
to:
!!FIleMaker 16: Changes Required??
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. If you have an older version of DayBack, you may need to make a change to get things working in 16. The first time you open %newwin% [[https://www.seedcode.com/filemaker-calendar/ | DayBack]], ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. If you have an older version of DayBack, you may need to make a change to get things working in 16. The first time you open %newwin% [[https://www.seedcode.com/filemaker-calendar/ | DayBack]], ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
Changed line 11 from:
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
to:
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. The first time you open %newwin% [[https://www.seedcode.com/filemaker-calendar/ | DayBack]], ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
Changed line 5 from:
This is a special url, prefixed with fmp, that is answered by FileMaker Pro (or Go) instead of by your browser. These URLs can contain scripts and script parameters and it is by opening URLs like this that DayBack Calendar can talk to FileMaker Pro.
to:
This is a special url, prefixed with fmp, that is answered by FileMaker Pro (or Go) instead of by your browser. These URLs can contain scripts and script parameters and it is by opening URLs like this that %newwin% [[https://www.seedcode.com/filemaker-calendar/ | DayBack Calendar]] can talk to FileMaker Pro.
Changed lines 9-11 from:
!!FIleMaker "Next": Changes Required
FileMaker introduced a new extended privilege in FileMakerNext that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in Next without this privilege enabled, you'll see this error:
FileMaker introduced a new extended privilege in FileMaker
to:
!!FIleMaker 16: Changes Required
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
Changed lines 9-11 from:
!!FIleMaker "next": Changes Required
FileMaker introduced a new extended privilege inFM16 that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in FM16 without this privilege enabled, you'll see this error:
FileMaker introduced a new extended privilege in
to:
!!FIleMaker "Next": Changes Required
FileMaker introduced a new extended privilege in FileMaker Next that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in Next without this privilege enabled, you'll see this error:
FileMaker introduced a new extended privilege in FileMaker Next that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in Next without this privilege enabled, you'll see this error:
Changed line 9 from:
!!FIleMaker 16: Changes Required
to:
!!FIleMaker "next": Changes Required
Changed line 24 from:
--> '''4.''' That's it! Click "refresh calendar" in DayBack and you should be all set.
to:
--> '''4.''' That's it! Click "refresh" in DayBack and you should be all set.
Changed line 24 from:
--> '''4.''' That's it!
to:
--> '''4.''' That's it! Click "refresh calendar" in DayBack and you should be all set.
Added lines 8-27:
>>comment<
!!FIleMaker 16: Changes Required
FileMaker introduced a new extended privilege in FM16 that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in FM16 without this privilege enabled, you'll see this error:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png | https://www.seedcode.com/rootimages/stikipad/dayback/urlerror1-2.png]]
The fix is simply to enable the new privilege. Here's how.
--> '''1.''' Select File / Manage / Security from the FileMaker menus.
--> '''2.''' Click on the "Extended Privileges Tab", then double-click the "fmurlscript" keyword.
--> '''3.''' Check "on" for any privilege sets you wish to be able to use DayBack.
--> '''4.''' That's it!
Why did FileMaker make this change? They believed that malicious users who knew your script names could trigger them from URLs even if you didn't provide buttons for those scripts. But users would still need to be logged into FMP with sufficient permission to run the script: the FMP URL doesn't bypass FileMaker security in any way.
>><<
March 02, 2017, at 08:47 PM
by - Removed link to DayBack troubleshooting docs since they link here for the fix
Deleted lines 7-8:
See our [[Troubleshooting | Troubleshooting Documentation]] for instructions on fixing FMP URL errors.
Changed lines 11-39 from:
to:
[[Version History | Version]] 9.69 of DayBack includes a test to see if FileMaker is listening for these URLs: if you see an error stating that the fmp:// URL isn't working, the best way to fix it is to uninstall and the reinstall FileMaker Pro. More below.
!! Testing & Fixing the FMP URL Protocol
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]]
->''Note: If you receive the message 'The file "DayBack.fmp12" could not be opened', you likely have renamed your DayBack file or embedded DayBack into your own file. In this case, you will need to copy this link, paste it into your web browser's address bar, replace the "'''DayBack.fmp12'''" portion with the name of your file and press enter/go.''
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...
-> '''Mac.''' Usually the Mac will open the URL in the highest currently open version of FileMaker. So all you may need to do is quit the version of FileMaker you don' want to be using. But you may be able to modify the launch services plist file directly. 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. This doesn't appear to be in the same place for every version of MacOSX.
-> '''Windows.''' If you've installed multiple instances of FileMaker, URL links will open, by default, in the last version of FileMaker installed. If you'd like to change the default FileMaker version that is used for FMP URL links in Windows, you can modify a registry key, rather than uninstall/re-install that version of FileMaker.
-> First, while this change should not affect your system in a devastating way, if you don't implement it correctly or modify/delete the wrong keys, you make render your system unusable. Therefore, a warning from Microsoft: ''Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.''
-> There is only one registry key value that must be modified for this solution. If you can't find this key in your registry, it would probably be best to just uninstall/re-install the version of FileMaker you'd like to open FMP URL links by default.
# 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@@
-> You may need to restart FileMaker to see the changes take effect. This change should update your system to open FMP URL links with the version of FileMaker you specified in the registry.
!! Testing & Fixing the FMP URL Protocol
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]]
->''Note: If you receive the message 'The file "DayBack.fmp12" could not be opened', you likely have renamed your DayBack file or embedded DayBack into your own file. In this case, you will need to copy this link, paste it into your web browser's address bar, replace the "'''DayBack.fmp12'''" portion with the name of your file and press enter/go.''
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...
-> '''Mac.''' Usually the Mac will open the URL in the highest currently open version of FileMaker. So all you may need to do is quit the version of FileMaker you don' want to be using. But you may be able to modify the launch services plist file directly. 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. This doesn't appear to be in the same place for every version of MacOSX.
-> '''Windows.''' If you've installed multiple instances of FileMaker, URL links will open, by default, in the last version of FileMaker installed. If you'd like to change the default FileMaker version that is used for FMP URL links in Windows, you can modify a registry key, rather than uninstall/re-install that version of FileMaker.
-> First, while this change should not affect your system in a devastating way, if you don't implement it correctly or modify/delete the wrong keys, you make render your system unusable. Therefore, a warning from Microsoft: ''Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.''
-> There is only one registry key value that must be modified for this solution. If you can't find this key in your registry, it would probably be best to just uninstall/re-install the version of FileMaker you'd like to open FMP URL links by default.
# 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@@
-> You may need to restart FileMaker to see the changes take effect. This change should update your system to open FMP URL links with the version of FileMaker you specified in the registry.
Changed line 1 from:
!! What is the fmp:// URL protocol?
to:
!! What is the fmp: URL protocol?
November 28, 2016, at 11:51 PM
by - Added link to troubleshooting documentation
Added lines 6-7:
See our [[Troubleshooting | Troubleshooting Documentation]] for instructions on fixing FMP URL errors.
Changed line 9 from:
Version 9.69 of DayBack includes a test to see if FileMaker is listening for these URLs: if you see an error stating that the fmp:// URL isn't working, the only way to fix it is to uninstall and the reinstall FileMaker Pro.
to:
[[Version History | Version]] 9.69 of DayBack includes a test to see if FileMaker is listening for these URLs: if you see an error stating that the fmp:// URL isn't working, the only way to fix it is to uninstall and the reinstall FileMaker Pro.
Added lines 1-9:
!! What is the fmp:// URL protocol?
This is a special url, prefixed with fmp, that is answered by FileMaker Pro (or Go) instead of by your browser. These URLs can contain scripts and script parameters and it is by opening URLs like this that DayBack Calendar can talk to FileMaker Pro.
The url protocol itself (the prefix) is registered with your operating system when FileMaker is installed. If you install more than one copy or uninstall lots of copies you can mess up this linkage of the URL with the most recent version of FileMaker and *no application* will answer the URL.
!! Errors
Version 9.69 of DayBack includes a test to see if FileMaker is listening for these URLs: if you see an error stating that the fmp:// URL isn't working, the only way to fix it is to uninstall and the reinstall FileMaker Pro.
This is a special url, prefixed with fmp, that is answered by FileMaker Pro (or Go) instead of by your browser. These URLs can contain scripts and script parameters and it is by opening URLs like this that DayBack Calendar can talk to FileMaker Pro.
The url protocol itself (the prefix) is registered with your operating system when FileMaker is installed. If you install more than one copy or uninstall lots of copies you can mess up this linkage of the URL with the most recent version of FileMaker and *no application* will answer the URL.
!! Errors
Version 9.69 of DayBack includes a test to see if FileMaker is listening for these URLs: if you see an error stating that the fmp:// URL isn't working, the only way to fix it is to uninstall and the reinstall FileMaker Pro.
