What is the best method to force a commit on another users specific file and table in a FMS shared environment?
I assume this arises because users are locking up records for undue lengths of time. Have you tried setting FMS to disconnect idle users after a set period?
[...with the understanding that such disconnects will cause their uncommitted edits to open records in any open windows to be lost.]
Correct, I do want to unlock the record (but not via a server disconnect)
I can probably use a remote Apple event or something. Not sure if I can can make it fool proof enough.
Hoping for some technique I've never heard of.
Correct, I do want to unlock the record (but not via a server disconnect) I can probably use a remote Apple event or something. Not sure if I can can make it fool proof enough.
This situation requires user training, not odd solutions.
Supposing you succeed. Now someone has made a big mistake and they have walked over to a colleague’s desk to find out how to fix it. Then nature calls and they go to the toilet. On the way back they are stopped by someone else. They finally get back to their desk and as they sit down to correct their mistake the record is saved and another user takes over. Let’s hope the error doesn’t cascade through the system as the erroneous data is used. (“Dr Hannibel Lecter? I see that you have been approved for early parole. You are free to go.”)
+1 to user training.
Indeed. I've had users specifically request a confirmation to save edits. Having the system save without asking would really upset them.
If possible also change the layout to also guide users to commit record changes,
For example popup/popover an edit window instead of editing data in a line in a list. That way users will want to close the popover to get back to the rest of the data when they've finished typing.
Even the addition of a simple "Save" button that just commits the record, so the user knowns its done.
Retrieving data ...