creating a runtime

[donhall]

ok, first, let's all pretend that i'm *really* dumb and need a step by step numbered, detailed explanation on creating a runtime on fmp 7 developer on windows xp home edition

it's a simple database, one file, a few fields, with sound clips in container fields...it just picks a random record and plays the sound clip.

5 fields, 3 scripts, a no brainer....i just *can't* seem to get a runtime generated....

thanx! ( see? i can't even spell thanks!....or can i?)

[transpower]

File | Developer Utilities | Add -- your only file | Project Folder -- specify the directory your wish to hold your solution | Solution Options | Create Runtime Solution application(s) | Runtime Name -- name your application | Extension -- choose a three-character filename extension | Specify GIF for closing splash screen (if you have one) | Delay -- choose no. of seconds for splash screen | OK | Create | test your new stand-alone creation.

[DykstrL]

1. Open FileMaker Developer Tool - this should bring up the Developer Tool wizard

2. Click Next

3. Check "Create a stand-alone runtime solution". Check any other options you desire.

4. Click Next

5. In the Specify Solution Files window either click add and select all of the FileMaker files that will be part of your runtime - OR - you can drag the files into the pane.

6. Click Next

7. Select the primary file from the drop down list. If you only have one file that should'nt be too hard. Here you can also specify a specific Help and About script that will work throughout your runtime solution. You can also rename the ScriptMaker Menu item.

8. Click Next

9. Under Runtime Name, enter the name you want the EXEcutable to be named. Under Binding Key, you can specify any number from 00000 to 99999. If you change this from the default (123456) write it down - it will be important later for upgrading your solution files.

10. Click Next

11. Enter the 3 letter extension for your runtime solution. If you change it from the default (USR), make sure you use an extension that is not associated with any other program installed on any computer that might possibly run your runtime.

12. Click Next

13. The wizard will display where the folder for your runtime solution will be created. You can change this by clicking on the Browse button and selecting the desired folder.

14. Click Finish

15. The Developer Tool will then generate the necessary files in the specified folder - the subfolder will be the same as your solution EXEcutable name.

16. When it's finished, open that folder and you will see that Developer has created 29 DLL files, 1 Help file, one EXE file and your FP5 file(s) now with the extension you specified in step 11 above.

17. You're not quite finished yet. There's one more step to do.

18. Go to C:Program FilesFileMakerFileMaker Developer 6Developer ToolRuntime Files - in there you will find a "system" folder - COPY that folder to your runtime folder.

19. Now to test:

20. Double-click the EXE file for your runtime solution. If you followed the above steps, your solution will open. The first time it opens, it will also register the Extension specified in step 11 to your EXE file.

If your extension is already associated with another program or EXE, it will not be changed - the file will still open with the other EXE or program. If your extension is sucessfully registered to your EXE file, you can also then open your runtime by just double-clicking any of the "USR" file(s) in your solution to open them.

21. Short and sweet.

[donhall]

thanx to both of you guys for the prompt advice

do i have to do anything about "kiosk" or menus or anything...i don't want the file modified in any way, and i have disabled as much as i could using access privileges etc

thanx again...

[transpower]

No, you don't have to do anything about Kiosk mode. But you may want to label the Script option something else; I use "--". I don't allow my users to independently choose scripts from the menu--so I don't display any scripts in the menu.

[Reed]

There is another option if you still want to use the script menu, but control which people can run the scripts and when they can do it. For each script in the scripts menu, just enclose the entire script in an If[] block containing the logic that contains functions like Get(AccountName) Get(PrivilegeSetName) Get(CurrentLayoutName) etc.

Of course if you pop for Dacons menu control, then you can make whatever menu items you want appear whenever you want.