Thanks for the update Jo. I’m glad you got it working.
We’ve seen this come up from time to time with developers, but rarely with end-users, because developers tend to install multiple versions of FileMaker on their system. This is why:
When you double-click an event, soSIMPLE uses the FMP: protocol to run the action script. That is it calls a url like: “fmp://x.x.x.x/your_solution?script=yourscript”.
Anytime you install FileMaker, the protocol preference is set up on your computer to open the version of FileMaker that’s being installed. So if you’re installing FMP14, the protocol will be set up to always open FMP14 (when opening an event in soSIMPLE for example). If you later open an already-installed FMP13, double-clicking one of your events might open FMP14. If you uninstall FMP14, then nothing will open. It sounds like that’s what’s happened to you.
There are workarounds to this that are good for developers to know about:
For Mac: RCDefaultApp
For Windows: Edit the registry for [HKEY_CLASSES_ROOT\FMP\shell\open\command] to point to the right installation of FileMaker.
Please always backup and be careful anytime you edit the registry.
