When a user is in a data-entry screen, I don't want them to jump out and do other things, because I have error checks in place to be sure they don't leave fields blank (incomplete entries are a major problem). I want to ELIMINATE their ability minimize 'within' FM (go to other dbs). I assume I can't eliminate the FM minimize/exit windows options altogether, but users tend to exit and then never come back and complete their entry.

I guess I can attach a script to shutdown of that db, checking the validity of the record, assuming they are still in it. Or could I attach it to the current layout? I want TOTAL CONTROL of the user or at least as much as possible. How do others handle this irritating ability of windows? By reading all of these posts, I know I can't totally control them, but can I at least WARN then if they leave before they're done?

One of the ways to accomplish this is to wrap your scripts in a Loop that will only exit if your validation criteria are met.

A basic example:

Allow User Abort (off)

Loop

Go to Field ["Field"]

Pause Script (indefinitely)

Exit Loop If [not IsEmpty(Field)]

Show Message ["You must enter a value into Field"]

End Loop

Show Message ["Thanks for entering a value!"]

Allow User Abort (on)

I'm not sure if this works as well in Windows as it does in Mac, but it's worth a shot.

Wow, thanks! Well, it needs to work in both, as this will be a cross-platform program. But I'm designing in Windows, so if it works in MAC and I can test that it works in Windows, I should be fine. Thanks SO much!

If you really want to control what your users do, consider building a kiosk. You'll have to provide all the navigation, buttons, etc., but the end result might be worth the effort. Note that you can only do this if your solution is single user.

I've been reading about this kiosk thing ... what do you mean by single user? A copy of FM on every computer? I guess I just don't know enough about that yet. Some users will access a server through a network (probably). Others will access through our website (and I'm not sure they will need FM on their home system). It appears that there are different ways to go here and I've been getting a bit lost. I don't want to invest in designing something that will have to be totally redone when it's web-accessible. Can you explain a bit more about that?

A kiosk removes the FM menus including the right-click context menu. The developer is then left with the task of providing all the navigation. It gives you total control over the solution.

The developer tool binds the database engine to your solution, after which you can freely distribute kiosks to everybody with them needing to have FM on their machines.

I'm unclear as to whether a kiosk could communicate with a server, either thru a LAN or over the web. Given how frustrating it is to deal with FM tech support and how uneven their support is, maybe Brent, Anatoli, Capt Kurt, etc. can comment on what it can do in a server environment.

To the best of my knowledge, kiosk mode is only availble in a runtime solution, which is not networkable. FM password options can be used to remove many of the menu options. The SecureFM plug-in can be used to remove more items and create different combinations. www.newmillennium.com/plugins.htm

-bd

This sounds like what I want. The question is ... is it worth it? Sometimes I think I try to protect users TOO MUCH and end up frustrating them (sorta like the old DOS programs) ... well, you MAC users probably don't know what that was like ... It just seems that everytime I get a call (usually late at night) it's because a user has jumped out of something, or gotton lost in the windows and can't figure out how to return to their work. Or some such crazy thing! If I can keep them where they should be until they are finished, then let them exit properly, it seems to work better from a data-entry standpoint.

Thanks Brent. I've added SecureFM to my wish list and will determine the order of it's importance later. I reviewed the website and also noticed Genesis (an accounting program). They want to replace their DOS Accpac (yuk, can't blame them). I'm downloading the demo now.

BTW, I LOVE your edit/reply button but when I right-click, save'as, I get the words along with it. I'd like to use it for most of my buttons and I KNOW it's okay with MAC and PC and all WEB views because it's here right? Any chance of grabbing it?

FYI, you can host files that have been bound as a runtime solution with FileMaker Server or a FileMaker client (with the standard issues involved with either). That is, FileMaker treats bound files as if they were regular FileMaker files. This includes those bound in kiosk mode.