When you select File | File Options...
What settings do you see selected on the Open/Close tab?
The runtime menu does not contain the File | File options.
The master file shows File | File options, with "Login using" unchecked and both the account name and password boxes empty. I change it to the runtime account name and password, then rebuild the runtime, but the result of no "Open" dialog persists.
"The runtime menu does not contain the File | File options."
True, but your development copy does and its settings are included in the runtime when you bind the files. If you need to change the settings, you change them in the development copy and bind your files again.
"The master file shows File | File options, with "Login using" unchecked and both the account name and password boxes empty. I change it to the runtime account name and password, then rebuild the runtime, but the result of no "Open" dialog persists."
If it is the account name and password in file options, this is exactly what should happen. If you've specified an account name and password in file options. Then filemaker will attempt to open the file with the specified account name and password. If the specified account name and password do not exist (say you deleted/changed the account settings after specifying your file options), filemaker will request a password when you open the file.
That makes sense and on reflection I did do some "tidying" of the menu recently, so this likely is where the problem lies.
I added the File | File options to the custom menu, but still get the same result.
"I added the File | File options to the custom menu, but still get the same result."
I don't see what relevance that has to the issue. File Options is needed to view and change the settings, but the settings will still be there and will control what happens when the file opens whether you can or cannot open this dialog.
I must agree as the problem persists... no security protection for the runtime.
Here's how I recently set up a run time:
Open development copy.
Update Accounts and Privileges
Set File Options to open the file with a limited use password without asking for a password by entering an account name and password in File Options.
Test the file by closing and opening it to confirm that it automatically opens with the desired limited access password. (The file does not ask for a password, it automatically opens itself with the specified limited access password.)
Once all testing is complete, bind the file--specifying the option to strip the full access password from the bound copy.
The resulting runtime opens without asking for a password, but opens with the desired limited access password.
I think my Filemaker program is corrupted.
I opened the solution file that I was building on my Mac, on my PC. The PC has it's own independent Filemaker Pro Advanced program.
The "Open " feature in the runtime works just fine on the PC.
I attempted to deactivate FMP on my Mac, so I could do a reinstall but it did not work after 10 minutes of trying. It ended by burping out the following message:
"A general activation error has occurred (50040)."
Looks like I'll have to call FileMaker tomorrow to get them to manually deactivate.
I share this conclusion in the event some other poor shlep encounters a similar problem, spending days banging their head against the wall for naught.
Thanks for your time. Just getting outside input prompted me to consider other options.
The files need to be bound to the filemaker executable on each platform. Did you do that?
The runtime works perfectly on the PC after binding on the PC platform (which is of course the only way it will run in that environment); discovered that late yesterday.
Further diagnoses rules out my hypothesis that the problem was with FMPA 9.
I have FMPA 8.5 on an old G5 running Tiger. I took a copy of the FMPA 9 development file to this system; it binds and runs perfectly on that system.
I copied the results and took it back to the Leopard environment; the runtime works perfectly from the copy.