If I'm not mistaken it is going to use the last one installed. The instlaler I'm sure registers the fmp protocol to itself. There may be a way to manipulate that (in the registry in Windows, not sure on OSX). But it is not going to be dynamic.
On Windows you can right click any database and choose “Open with …” and then “Choose default program …” to tell windows what program to use as the default for opening files of a given type (extension).
Peace, love & brown rice,
FileMaker + Web: Design, Develop & Deploy
Certifications: FileMaker 9, 10, 11 & 12
Member: FileMaker Business Alliance
One Part Harmony <http://www.onepartharmony.com/>
Austin, Texas • USA
Yeah, that is what I thought, but it opened Filemaker Pro (which came "pre-installed" on our company mac image)... But may I installed an updater later hmmm... I just ran the 13.0.3 updater but alas....
1. if fmpa 12 is open and I open the WebViewer database in fmpa 13 the fmp:// targets fmpa12.
2. if only fmpa 13 is open with the WebViewer database the fmp:// targets fmp12.
Yep same on the Mac... (standaard = default)
I have Filemaker 13 selected, but alas it doesn't use that one. I think it's time for some under the hood digging :-)
I don't think 13.03 is a "full" updater, and thus may not reset the program associated with the FMP12 protocol.
I suspect that if you uninstall FMP 13 and reinstall, FMP 13 will become the default app for the FMP12 extension.
Nope, reinstalling didn't work... too bad hé...
But I solved it by going under da hood...
there is an array call LSHandlers and a sub-array LSHandlerURLScheme... There you can edit it. That was indeed pointing to fmp and not fmpa13.
Now I get different error... But's that's because we are using roaming profiles... Just need to change the fmp:// call to solve that...