You have to create a version specific to each platform - Mac on Mac and Windows on Windows. A Mac-created runtime will not run on Windows and a Windows created runtime will not run on the Mac.
Next, you can't run off of the CD if you want to add or edit records in the database. The CD is read-only. So you'll likely want to find yourself an installer application to copy the files to the correct folders on the hard drive of the user.
Once created, the user will not requrie FileMaker - the runtime takes care of that aspect.
OK, three issues.
Here's one more - with a runtime all of the data files are stored in the same folder as the created application. If you issue an update to the runtime application be sure to build in some kind of export/import in order to transfer any added data to the new version.
1 of 1 people found this helpful
I think you can make a Hybrid CD with Mac and Windows part. I used Toast app years ago to make this. The benfit is that each platform sees only its files, but still you can have shared files for both. So your databases can be on the CD only once for both.
If you are careful to use the exact same binding code for both the Mac and Windows runtimes, the datafiles from one can be rebound into the other, and then distribute the twice-boudn data files in both of the runtime packages. This will allow a user to move their data file between OS versions if they need to use it on both systems. They will still need both runtimes, eah installed on its own platform, but the data file itself will be cross platform.