AnsweredAssumed Answered

trigger FileMaker Script via URL does not work properly

Question asked by seevogel on Jul 26, 2018
Latest reply on Aug 21, 2018 by seevogel

Like • Show 0 Likes0
Comment • 4

If 2 or more FileMaker Versions installed on a client computer (for example fmp 16 and fmp 17) triggering a script via URL does not work properly depending on the FileMaker Version where the FileMaker file was launched with.

so:

if I open the file Clients.fmp12 remotely (from server) with fmp16 and then sending an URL:

fmp://~/Clients.fmp12?script=ListClients

then the script from the same file will be triggered correctly.

When opening the same file with fmp17 remotely and then sending the same url, FileMaker 16 will be launched and a message appear 'The file "Clients.fmp12" could not be opended. Either the host is not available, or the file is not available on the host.'.

The FileMaker Version wich will work correctly may depend on which FMP Version has been installed first or last.

No one else has this question

Outcomes

JEDtech Jul 29, 2018 5:44 PM

We have noticed that at least on Mac installation of FMPA 17 it does not claim the "fmp" URL if other versions remain installed. You can adjust this behavior with installation of the old but free and still functional RCDefaultApp 2.1 Preference Pane by Carl Lindberg

Actions

seevogel @ JEDtech on Jul 29, 2018 7:08 PM

Sometimes I open the database with FMP 17 and sometimes with FMP 16.

Ideally it should work with both versions instantly.

Will RCDefaultApp 2.1 provide that behavior?

Actions

JEDtech @ seevogel on Aug 21, 2018 7:17 AM

The database can still be opened with any supported version. What RCDefaultApp does is associated an App with a file suffix so that by default that's the one that will open it when you double-click on it. If however for example you have associated the .fmp12 suffix with FileMaker Pro Advanced 17 but you have FMP 16 open (and not 17) then it will open with the currently running FMP 16. If you have them both open and are using URLs from Web Viewers it will go to the one set as the default so potentially if you click a URL in 16 it will attempt to run in in 17.

Actions

seevogel @ JEDtech on Aug 21, 2018 7:47 AM

thanx.

I now have RCDefaultApp installed and I am able now to decide if FileMaker URLs open with FMPA 17 OR FMPA 16.

That makes things a bit easier and I have to flip that behavior only if changing to develop with the other version.

Generally the situation is as follows:

I keep both versions open.

I develop with FMPA 17 and have some helper Databases open with FMPA 16 where I keep my timetracking, calculations etc.

(I can not timetrack in the same App if the Database Window is open)

I have a similar problem with shortcuts:

I defined some shortcuts in macOS System Preferences (Keyboard).

Unfortunately those shortcuts depend on a specific Version of FileMaker and If I define them for FMP 17 they do not work with FMP 16. I also have to re-define those shortcuts if a new Main Version of FileMaker has been distributed.

I define shortcuts for: open Window, open debugger window, open data viewer, align object size, Define Object Trigger, Conditional window, Value list, custom functions, layout setup, custom menus and others.

Actions

4 Replies

JEDtech Jul 29, 2018 5:44 PM
Mark Correct
Correct Answer
We have noticed that at least on Mac installation of FMPA 17 it does not claim the "fmp" URL if other versions remain installed. You can adjust this behavior with installation of the old but free and still functional RCDefaultApp 2.1 Preference Pane by Carl Lindberg
Like • Show 0 Likes0
Actions
seevogel @ JEDtech on Jul 29, 2018 7:08 PM
Mark Correct
Correct Answer
Sometimes I open the database with FMP 17 and sometimes with FMP 16.
Ideally it should work with both versions instantly.
Will RCDefaultApp 2.1 provide that behavior?
Like • Show 0 Likes0
Actions
JEDtech @ seevogel on Aug 21, 2018 7:17 AM
Mark Correct
Correct Answer
The database can still be opened with any supported version. What RCDefaultApp does is associated an App with a file suffix so that by default that's the one that will open it when you double-click on it. If however for example you have associated the .fmp12 suffix with FileMaker Pro Advanced 17 but you have FMP 16 open (and not 17) then it will open with the currently running FMP 16. If you have them both open and are using URLs from Web Viewers it will go to the one set as the default so potentially if you click a URL in 16 it will attempt to run in in 17.
Like • Show 0 Likes0
Actions
seevogel @ JEDtech on Aug 21, 2018 7:47 AM
Mark Correct
Correct Answer
thanx.
I now have RCDefaultApp installed and I am able now to decide if FileMaker URLs open with FMPA 17 OR FMPA 16.
That makes things a bit easier and I have to flip that behavior only if changing to develop with the other version.

Generally the situation is as follows:
I keep both versions open.
I develop with FMPA 17 and have some helper Databases open with FMPA 16 where I keep my timetracking, calculations etc.
(I can not timetrack in the same App if the Database Window is open)

I have a similar problem with shortcuts:
I defined some shortcuts in macOS System Preferences (Keyboard).
Unfortunately those shortcuts depend on a specific Version of FileMaker and If I define them for FMP 17 they do not work with FMP 16. I also have to re-define those shortcuts if a new Main Version of FileMaker has been distributed.
I define shortcuts for: open Window, open debugger window, open data viewer, align object size, Define Object Trigger, Conditional window, Value list, custom functions, layout setup, custom menus and others.
Like • Show 0 Likes0
Actions

trigger FileMaker Script via URL does not work properly

Outcomes

Related Content

Recommended Content