What's best option for this solution...

[duncandawg]

I'm just about finished building a solution which I wish to offer access to about ten users at once. My solution is rather complex (in that it has a menu driven system of multiple related files). I've built my own Log-in and password management system (in-spite of reading many more cons than pros to this) and I have attempted (so far) to make the User Interface as simple and intuitive as possible for my less computer literate colleagues. So my goal is to give users as little access as possible to the usual FileMaker features, while having them use my scripts and buttons as much as possible. While at the same time, I may wish to modify parts of my solution as it is rolled out, yet not losing any data which gets input in the meantime. Here is my dilemna/question:

I am not sure which is the best approach to take for serving this solution. Should I Bind all of the files with FMP Developer - and if so, do I want Kiosk, or stand alone modes? I wish to limit as much as possible any of the usual elements of Filemaker which are available to the end users. Should I serve this over a server using FileMaker Pro Server? If I do it this way, will I be able to "unbind" the files later and modify the scripts and layouts etc. And if so, will I maintain integrity of all of the data which gets added in-between my fixes/rebuilds?

Or is FileMaker Unlimited the way I should go? I've reviewed some of the product features on the FileMaker Web site, but I'm still a bit unclear as to which of the FileMaker Products will best suit my needs on this matter.

Anyone have any suggestions as to how I ought to proceed?

Thanks,

Chris

P.S. I tested out my solution over a local network, using one FMP Client connecting to another (which acted as the host) and I ran into a few glitches when scripts called for other Files and the guest machine was having difficulty finding the original file. It seemed to be looking for the secondary file locally, and not on the host machine. But when I went back into my scripts on the host machine, I found that the secondary file was being pointed at correctly. I'm guessing by Binding the files, this problem will go away, as well as menu bars etc. which I am trying to keep away from the end users.

I hope I am making sense here.... anyone care to help me to clarify this situation?

Thanks again.

[Pupiweb]

You can't use a runtime since FM runtimes are not networkable; FMU is a normal FM5 client with no IP limits for web publishing

Given the number of files and of users you definitely need FM Server, ideally on a dedicated machine, system file sharing religiously OFF

ALL users enter the solution with a (default) limited password and their actions are ruled by the privileges written in the Users.fp5 file you've done

Up to your security/protection concerns whether to put on the server a copy of the files after you've removed (with the Dev tool) the possibility of accessing fields, Layouts etc ...

[GusCoombes]

Can't tell you much about binding, but if you only want to serve to about 10 users on a LAN, get FMPro Server and run it on a standard Mac OS machine - which should run nothing else at the same time - as the previous poster said, no filesharing. Just a plain vanilla system with as much turned off as possible.

My guess about the binding would be that you don't need to do it with Server, as the Server is optimised to look after multiple files and clients on a LAN. Serving over the Internet or a WAN - maybe you need Unlimited and binding.

My experience is, if you need to do maintenance you can grab the copy of your files that Server will make periodically (you can set this up as you need in the preferences). Once you've edited this, you may have to re-import your data if the users have been changing stuff in the meantime, but you shouldn't have any problems otherwise.

[Kurt Knippel]

Binding the files into a runtime is really best for packaged single-user solutions, where you do not want to users to have to purchase a copy of Filemaker Pro.

Binding simply associates a set of Filemaker files with a particular runtime engine, so that you could have multiple bound runtime applications and they would all keep themselves seperate. Binding does not prevent the files from being opened and/or modified in Filemaker Pro.

You situation is pretty much the basis for Filemaker Server, with normal copies of Filemaker Pro connecting to unbound files.

[duncandawg]

Thanks to all of you guys for your replies. I think I'm almost clear now. If I understand correctly, I should use FMP Server and allow regular versions of FMP to connect to it. Run it on a mac with no other connections (FileSharing OFF).

My only remaining question, is whether or not FileMaker Developer is of any use here. Am I still able to use it to eliminate some of the users' access to the entire file?

Pupiweb stated:

"Up to your security/protection concerns whether to put on the server a copy of the files after you've removed (with the Dev tool) the possibility of accessing fields, Layouts etc ... "

How do I use the Dev Tool to limit access and still serve these files? I understood once I used the Dev Tool, the solution becomes a "Runtime" which I am now understanding - can't be served??? Am I still missing something?

Thanks Again,

Chris

[kenneth2k1]

FM Developer contains the Developer Tool which allows you to do these things:

1. Create a runtime. A runtime will run independent of FM

2. Create a kiosk. Kiosks are similar to runtimes but will appear full screen (I suppose for touch screens, restaurants and such).

3. Rename related files and links

4. Permanently prevent modification of a database structure

5. Utilize custom "About" and "Help" menu options.

6. Add/ remove .fp5 extension.

Although I have not tinkered with em, I understand that Developer also comes with resources to make button effects and a sort-of popup help when you focus the pointer on something in your solution.

If any of these sound helpful, I would look into it, but it sounds to me like you are going to have a network solution, and, as stated before, you cannot network to runtimes. Developer doesn't sound helpful in this case.

Ken

[Pupiweb]

You can use the Dev Tool to create runtimes or kiosk solutions that will run as standalone applications (IOW no Filemaker needed) but cannot be networked ... this is not an otion for you since you want to use your solution over a network

Another function of the Dev Tool is to permanently strip off the possibility of modifying file structure: this means that the files will have to be opened by a regular copy of FileMaker or kept open by FM Server BUT nobody will be ever capable of making changes to them ... great option for demos, btw ....

Since you manifested some concerns about protecting your work this might be an option ... the shortcoming is that making any change even minimal will force you to use an open copy of the file in which you'll have to re-import the data of the working files ...