AnsweredAssumed Answered

Runtime solution scripts that are set to run with full access are being chalanged.

Question asked by CstDskSol on May 31, 2015
Latest reply on Jun 30, 2015 by TSGal

Summary

Runtime solution scripts that are set to run with full access are being chalanged.

Product

FileMaker Pro

Version

14

Operating system version

Windows 7 Pro and Current Mac os

Description of the issue

I have a runtime solution that has a script that is set to run with full access. When the script is triggered from a remote computer, also running Pro 14, it asks the user for an account name and password over and over, doesn't even accept admin credentials.
This script runs fine if both computers are running FMP 13.
Note:
While building my runtime solutions, I change the file extension to ".ddd"
If I test the script using the unbound .fmp12 files (prior to binding) it works fine on both computers.

Steps to reproduce the problem

Create a simple script.
Make sure it is set to run with full access.
Bind the file into a runtime solution and change the extension.
Open it using FMP14 to host it.
Open it remotely on another computer running 14.
Run the script.

Outcomes