I've seen this one before but forget what the resolution was.
What happens if you double click the database file instead of the appliation?
The error message suggests your application is set up to open a database file named "debug" that it can't find as part of the run time's set of files.
Yes I found that initially as well. Same message but different problem and on OSX. Clicking an fp7 opens in FM11A just fine. Clicking Runtime.app get me the message. I tried dropping an fp7 on Runtime.app as well and no luck.
Both sytems can have issues with matching the correct file with the correct application when a file is double clicked. Thus, the same solution may apply in both cases though I'm suprised to see exactly the same error message here.
Let me rephrase: With your runtime app, you also get one or more database files--usually with a .USR extension but this can be changed by the runtime's creator. (It shouldn't ever have .fp7 as the extension.) What happens if you double click the runtime's database file?
Sorry I guess I am not being clear. I cannot even open Runtime.app to create a runtime solution. I get the error trying to open Runtime.app.
This is what terminal returns when I get the error message...
2011-07-28 14:06:01.384 Runtime[19235:903] Can't open input server /Library/InputManagers/MultiClutchInputManager.bundle
To create a runtime solution, you launch FileMaker Advanced and select "Developer Utilities" from the Tools menu.
Runtime apps are not used to create runtime solutions.
You use FileMaker advanced to create a runtime solution. When you do this, FileMaker makes a copy of the local machine's FileMaker app, but "crippled" so that this copy can't be used to make design changes to database files. (This would be the "runtime app".)
It then makes a copy of the database files as specified by the developer to be included with the run time in a folder that includes a large number of utility files.
Thus, you should have a folder of files provided as the run time solution. In that folder should be found both the "crippled" run time application file and also the database files "bundled" with it.
Well duh :P I don't know how I got my self stuck on even thinking I needed to use Runtime.app; this isn't the first time I have made one. Thanks
I attempted to create a runtime solution and everytime I tried to run it I got the message about the missing DEBUG file. I think this problem occurs because of the method that the Developer Utilities uses to create runtime solutions.
I opened the Developer Utilities and added scouts.fpm12 as my database file but did not rename it so the name of the database file for my runtime application remained "scouts". I then clicked on Specify Project folder and selected the location for my solution. Next, I clicked on specify Solution Options and clicked on "Create Runtime solution application(s)", made the runtime name "test", and clicked OK.
Next I navigated to the Project Folder and found my solution. The complete runtime solution was in a folder called "test" that contained scouts.fmpur, an extensions folder, a pdf file, and test.app (the runtime solution application). Naturally I then clicked on scouts.fmpur but got the missing DEBUG message and my solution did not run. The problem is that the first time I ran my solution, I needed to click on test.app (the solution) rather than scouts.fmpur (the database). When I clicked on test.app, the solution ran properly. After the first run, I could then click on either test.app or scouts.fmpur and the solution ran.