2 Replies Latest reply on Dec 5, 2012 9:24 AM by philmodjunk

    How does FMP Advanced Kiosk work?

    wilz

      Title

      How does FMP Advanced Kiosk work?

      Post

           IS this how the FMP Advanced Kiosk feature works????

           Say I have have 5 computers, and they are all networked (in an office) 

           One computer has FMP Advanced, and I create a database on it. I then create a  "runtime stand-alone Kiosk" and install it on the other 4 computers.   The other 4 computers can access the FMP Advanced Database through the kiosk (and update / make recoreds on it). 
           The Limitation of Kisok is that there is no actual abaility to "modify" the database (i.e. make tables, change appearances etc... 

           OR do I have to get a license for all 5 computers?
           I read the help files, but im just a bit confused still. 

           Thanks! 


           from FMP Help: 

            

      A FileMaker database that runs full screen, without toolbars or menus. Users click buttons to navigate. In FileMaker Pro Advanced, use the Developer Utilities to create Kiosk solutions. You can bind Kiosk solutions into stand-alone runtime solutions.

        • 1. Re: How does FMP Advanced Kiosk work?
          schamblee

               You have to have a license for all 5 computers.  Runtime solutions are stand-alone.

          • 2. Re: How does FMP Advanced Kiosk work?
            philmodjunk

                 What you describe will work and not encounter licensing issues--at least you won't trip error messages and the files won't crash, but it may not produce the results that you want.

                 What you describe puts a completely separate copy of the database on each user's computer. Any changes made to the data by one user will not be visible to any other user as each has their own copy of the data.

                 And runtime solutions cannot access the same hosted database as clients of that database--you'd have to use correctly licensed copies of FileMaker Pro to do that.

                 So this works only if the "flow" of data is one way, from your original database to the individual users. If you need to collect the data they enter into the files after the fact and merge them back into a centralized copy, that can be done, but managing multiple versions of the same record--say it was modified in different ways by two or more runtime users, is not a simple matter to deal with and fully avoidable if you host the file over a network.