Can someone steer me in the write direction?

I need a relogin scheme for a single file solution, shared (FM8, peer to peer) on two or more computers, used by 6 different users.

I thought the relogin script was great until I noticed a false account name, or cancel returns the user to the current account.

1. The main reason for the login is an audit log. I need to capture a user name. I currently use the account name when populating the audit log.

2. Security: some accounts have different privileges. However, daily operations to not require anything more than the same base level privilege set. Although, I would hate to restrict future development to one privilege set.

3. Ease of use. I suspect the users will rebel or not login/logout if they must type both an account name and password. Is an easier login possible? Can a automatic logout be scripted for inactivity.

Any suggestions? I prefer to use system features whenever possible; how much externalization may be required here?

One thing you can do is have FM Server automatically disconnect idle clients, then users have to log in and will be disconnected if they just walk away. Just have an opener file in the dock, or on the desktop which attempts to open your hosted file.

If you want to leave the file open after logout, just use a relogin to a dummy account that has no privilges except to relogin again as a different user. If you will have a few standard users and they're too lazy to type both their account name and password. Just display all the users' names in a portal on the dummy login screen, and when the users click on their name in the portal to login, it will populate the pw dialog with the correct username, and they just need to type the password.

If you're not using server to disconnect idle clients or you want to automatically relogin to the dummy screen after inactivity, you'll have to carefully script your interface, and likely use a script scheduling plugin to schedule the logout script to run x minutes after each user action. If they perform another action, the current schedule will be erased, and the system will wait x minutes again....

I've got a solution where many users may use the same machine one right after another (hospital nurses doing charting).

I found the same problem usingthe re-login where it can be cancelled and it returns to the orginal user. Very bad.

So here's what I did.

1. Create an account that has NO privlages except to modify a single global field to count the attempts at log on.

2. Then create a layout with NO menu items with a splash screen type of background.

3. Create a script that goes to the new layout, then Re-Login to the NO Access account, followed by the re-logon step. That way if the user cancels the re-login dialogue, the account is a No Access account!

I added a few extras that count the attempts in a global field and then after a number of unsucessfull attempts it gives the user a message and pauses the script for 60 seconds.

Mine also has a loop that runs the script again if the account name=NoAccess acount name that I had created. That way, if the user cancels the re-login, it goes back to the no access acount and then goes through the re-login process again and again until the user sucessfully logs in.

ReLoginExample.zip

Thanks for the help. After posting my message and playing a bit I realized I was in for another workaround. Bruce, the example file is appreciated. It is always good to see it in action. Thanks again.