Thank you for your post.
If you have a local file and try to open a Remote file, FileMaker Pro will try to launch using the existing "generic" account. If that account doesn't exist, then FileMaker Pro prompts you for the account.
Therefore, a generic opener file will only work if the account being used does not exist in External Authentication. Otherwise, each opener file would need to be customized to contain the specific user account that exists in External Authentication.
I would also recommend reading the Server External Authorization White Paper at:
Can't open the white paper, get a permission denied message.
Thanks for your post. Since I'm inside our company firewall, this may be the reason. Instead, try downloading the White Paper through Knowledge Base Article #6822 at:
Is it sufficiently up to date? It refers to Server 8 (in the PDF's file name) and server 9 in the Products list.
We figured out a solution that appears to work. After setting up external authentication according to the above whitepaper, we did the following. Our environment is Windows based.
Created a batch file that has the following entry (I imagine the same can be done in AppleScript):
start "C:\Program Files\FileMaker\FileMaker Pro 10\FileMaker Pro.exe" fmp7://<servername>/philtest
We are able to place the batch file on a shared network drive and give everyone access via shortcuts on their desktop.
I also found a utility called BatchtoExe that allowed me to compile the batch file so that nobody could open or edit the batch file. I hope this helps others.