I am trying to understand how this binding etc works.

IF I bind all the files together that are on the FMS, and then distribute the solution.exe, is it still connecting to the FMS just like if I open it in FMP?

What exactly does KIOSK mode do for me?

Hi:

You cannot network runtimes. Not unless each workstation opens the runtime with FM using the hosts dialog. This leaves you with a couple of options:

1. have a copy of FM for every client.

2. consider a web based solution

A kiosk is used mostly in like a retail situation. When it is opened, it takes the entire screen area, and is good for touch screens and stuff.

That is probably why the creator of this application couldn't get it to work. Wonder why he just left it broken? Of course then I wonder why he was paid a couple mil to do it in the first place when he was clueless about such things as database design. Oh well.

I guess it might be good for you to know that I have seen companies that sell bundled apps made with FileMaker that are networkable. However, they are not runtimes. What they do is resell FM with their product, and in the installation the person specifies if the PC is a host or client. Their installer would install FM first, then install the solution.

So this is a possible scenario.

Ken

Don, if I recall from your other posts, you are running FM version 3. In version 3 you could network runtimes. Starting with version 4 or 5, runtimes could no longer be networked.

Hmmmmm. I'll look closer.

No. It doesn't work. When I try to open another file it says it can not because it is not part of the current solution. I don't want the outside file to be part of the runtime solution.

This is baffling. The original author was able to bind 1 file that called another file and did NOT get the "this file is not part of the solution" error.

All he left was the binder itself. If I had the entire thing would it then allow me to make a runtime that could talk to files outside of the solution? Or is there something I'm missing here totally?