We do use the "Select File" function - registered as variable with the 360 works Scriptmaster 5.1 plugin - in our FM database.

This works fine up to FM16. When you open the same database with FM17 the dialog window is in the background and Filemaker will get stuck as it waits for the input in the window that is not visible to the user. The problem also exists with the new 5.2 version of Scriptmaster plugin.
If you execute the function in the "ScriptMaster_16+.fmp12" sample database the dialog is in the foreground (as it should) - if you select the option "Register on startup" or if you register the function via clipboard the dialog is in the background.
Did anyone find a workaround for this problem?

Best regards,

Martin

I'm running in the same issue and it is very confusing for the user. The system looks like it is frozen but it is actually waiting for input into the dialog window they cannot see.

It is all the more annoying when the access is via RemoteDesktopControl and the user only gets to see the FileMaker window. There is no way they can reach the dialog window.

Any solution to this would be greatly appreciated.