i made a runtime soution last month and all goes right. Now i made the second version of the application and export to a runtime solution, but when the user open the file it crash. What could be the problem.
i use filemaker 15 adv.
what error are they getting exactly? Did they cleanly remove the first one before using the second one (to avoid named file conflicts)?
A window dialogue box that say that the file produced en error and cannot be execute. I opened the file to a machine that never execute the first file and it opens right the soultion. But on machines where i opened the first solution dont work. I read that the runtime solution install something on the system, could be this the problem? If yes what files i need to remove?
Should be covered in the documentation here:
I’m not entirely sure what the process is, it’s been over 5 years since I used a runtime myself.
In windows, it's a matter of binding code checking and file extensions.
When you double click a runtime File, the OS looks for the application associated with that file extension and launches it. On a computer where you've opened the first run time solution, this will be the .exe runtime app for the first solution. It will launch and compare the binding code specified for it with the binding code specified for the file that you double clicked. You get an error message if they do not match.
what can i do now?
I forget the details, but you can go into your OS settings and change what application is specified as the default application for a given file extension. You can use this OS feature to open the exe file from the second runtime instead of the first.
You can also re bind your runtime solution and use a different file extension so that they both do not have the same extension.
A third option is to launch the runtime by opening the .exe file instead of the run time database file. The application will correctly find and open the associated runtime file for you. I would think that if you use an installer utility, you could even put a shortcut to the .exe file on the user's desktop to use to launch the runtime and keep the physical file hidden away where they won't try to launch your runtime by double clicking it.
I already try to rebind the solution with different file extension but crash. I always open the solution from the .exe, because if i open the file with .fmpur it ask me to choose an application to open.
Then it may be that your file is damaged. Run a recover on it. I'd recover the original copy used to produce the run time set and see if I get any problems reported by the recover process and, unless I get a "do not use" message, I'd then produce a run time app from that recovered copy and see if it still crashes.
Retrieving data ...