Filemaker who is logged in

You could set up a table and a script performed by the OnFirstWindowOpen trigger. The script can create or update a record in the table with a user's account name each time they open the file.

A similar process can log them out when the file is closed, but this doesn't work in event of a crash or force quit. And I stated as much to my superiors. But this is the reality I am in, so it is what it is. These usually are quite safe to do, but can catch a user "between chairs" if the interface suddenly changes on them in the middle of a task that they are completing.

Keeping such changes incremental and having good communication with your users helps a lot with keeping these changes happening smoothly. The same "caught between chairs" issue applies, but now, there's a very small added risk that a glitch might happen and not be noticed that takes place right when you commit the change back to the hosted file which might introduce latent file corruption.

I consider these much more risky. Not only do all of the above concern applies, but other users are locked out of a table while the changes made to it are applied once you exit Manage Database by clicking OK.

I haven't tried it since FMP 10, but it used to be that simply opening the calculation dialog to inspect an auto-enter calculation locked everybody else out of the field's table until you closed that dialog.

A script is triggered on server, which runs the command line utility to query the list. One correction: If there are no auto-incrementing fields, then users are not locked out while the developer is making changes. On the contrary, they are indeed locked out once you click OK during the time that the changes get saved back into the hosted file. On the flip side a developer can be locked from making changes to the schema if a user is editing a field.

Live editing while in use should be done with caution. I've created a Login Table and when a user opens the file, the on first window open script creates a login record which contains lots of information.

When they quit, the record is marked logged out. IF the server is closed and reopened then all records are marked as logged out if needed. It would be easy to perform a find on that table and display the results in a report in a Card or Dialog or Floating window I will give this a try tomorrow if I can get permission from the higher ups to install the BE plugin on the client's server.

FileMaker Pro. FileMaker Server. FileMaker Go. Custom Web Publishing. FileMaker WebDirect. Runtime solution. All postings and use of the content on this site are subject to the Claris Community Use Agreement. Search Loading. Register Login. View This Post. Edited January 29, at PM. Here is the script as of version 1.

This content is a preview of a link.