Does this need to be done in FileMaker Admin Console?
Go to the Activity tab, choose Clients. Select the client in question, then click the envelope icon in the upper right-hand corner. Select "Disconnect".
Doesn't matter. If the session is hung and they have an open record, terminating it from the Server end can still corrupt the database.
Best practice is to ensure that records are committed on a regular basis, but you can't always control that.
I completely understand what you are saying but the person above will go off the rails if an employee calls me up saying their frozen and I go there and do ctrl+alt+delete. Do you know what the steps are in Admin Console?
Completely off topic, I am taking FileMaker Classes with TheSupportGroup in NYC. Have you heard anything about them?
Nope. Sorry. Maybe someone else can give you some insight.
YES! There are several good training groups for FileMaker. You will have an excellent experience.
"Corrupt" is a word that means many things. Like "love" and "pizza". I don't think killing a session, either locally or on the host will "corrupt" a database (unless possibly if you have unsaved schema changes). It make screw up that particular record, I'm not sure, but "corrupt" contains a certain connotation that the whole database and hosed. I don't think that's the case here.
Not usually, but I've seen it happen, so it can.
Is there a reason why people on here need to be arrogant? I'm new to FileMaker and I'm asking basic questions because I don't have the answers. I may not have written the question with the proper terminology but that is still no reason for arrogance. For everyone else who responded and was helpful I appreciate you taking the time out of your day to respond to my question.
Retrieving data ...