Are you trying to open a file that is already being hosted on a nother computer/server, or are you trying to open a local file to be hosted via the computer that is starting up?
You could create a launcher file which, when opened, uses the correct account credentials to open the other file, place the launcher only on that machine, and set that file to be opened at restart.
Thank you for your reply.
To answer your response:
1. We are trying open file locally to be hosted via the computer that is starting up.
2. We have the launcher file (which is the file we are trying to open) that it turn launches several other files via a startup script (no problem there) using the correct credentials.
The problem that we are seeing is that the launcher file is not wanting to launch unless it is clicked on (when restarting OSX Lion). The Filemaker splash screen appears and disasappears (as normal), but then the Filemaker App Icon just bounces in the dock waiting to be clicked on. This didn't happen with Filemaker 11 Pro, which makes me think that something changed with Filemaker 12 Pro. Thoughts?
I would have the launcher file open only one file, and have a startup script in that target file that opens all the others.
Be sure that the account creditials in all files match exactly so none of them have a hidden login window needing attention.
Have heard other Lion issues similar to this, but account credential issues were behind at least some of them.
1 of 1 people found this helpful
Also check that startup scripts in the various files do not fire when this account launches the files, other than the opening of the files from the launcher and the first file.
Those onOpen processes may be creating an issue with simple file opening. After all, you are wanting this computer to act as a Host, not a client.
[ And think about moving to Server, which will solve the problem and be much safer for your files. ]
1 of 1 people found this helpful
Thanks - we will check this out and let you know how it goes.
I believe it is a case of FileMaker wanting to be the foremost application before it will open the file. Other login items that launch after FileMaker, or take longer to open can come to the front and make FileMaker pause. Consider removing other login items, or setting them to "hide".
If that does not work you can open the launcher file some time after login, using either a launch demon (Lingon is good for that), or an AppleScript with a timer that is opened at login.
Hello Bruce (and Steve),
We are still having problems with this particular issue; there are no other startup items for this login (under system preferences). However, it is now acting very strangely: sometimes the file will launch as desired (unattended, no bouncing app icon in dock) and other times it needs a click or some interaction with the bouncing icon to launch the file. Any thoughts on why this might be? It almost seems like there is a bug or something going on between Filemaker 12 and OSX Lion.
Any guidance on writing a simple Applescript to do the user interaction for us (I've never had to write Applescripts before, but have quite a bit of experience with Windows VBA, SQL, etc.)?
I would greatly appreciate any thoughts or ideas that you might have.
Here is one I use, created in Applescript's Script Editor, saved as an application with no startup screen. That application is then set to Open at Login.
tell application "Finder"
open alias "Macintosh HD:Users:user:Documents:LauncherFile.fp7"
300 is the number of seconds, 5 minutes in my case. You will probably want something shorter, try 30.
Hello Bruce (and Stephen),
Taking this approach worked perfectly - thank you very much for your help.
This almost appears to be certainly a bug in Filemaker 12 Pro, as even trying to launch the Filemaker 12 Pro app by itself at startup; produces the same results.
Thanks again for your help!