The "runtime" is nothing more than a special version of the Filemaker application, which is limited in functionality and tied to a particular set of database files. There is no more harm or benefit in opening it first, than there is in opening the Filemaker application first.

From a support standpoint, I always used to have my file in a folder inside of the main installation folder. I then had the installer put an alias/shortcut in the main installation folder along with readmes, licensing and such files. This way the user never really even saw the actual database files.

The binding key you install in the creation of the runtime, e.g.8765789, is what ties the files together. On the Windows OS, the three digit extension pays a role as well, especially if the files are later used on FIleMAker Server.

As Kurt says, there is no difference practically speaking in what happens. Clicking on the runtime engine opens the primary file first; that is the recommended practice.

HTH

Old Advance Man

I've developed a runtime solution that will be distributed to novice computer users. I was under the impression that the only way this solution would work would be by clicking on the runtime solution. Under my imression, clicking on the data file would cause some sort of explosion or error.

In reality, the supporting data file looks, smells, sounds, and feels just like the actual runtime. What is the harm of a customer repeatedly working within the data file as opposed to working in the runtime?