If a user get disconnected to the server will connected to FM Server, FileMaker Go will attempt to reconnect to the server. This works well sometime but other times it can be extremely problematic. It appears either FM GO or FM Server gets confused and thinks that the record is locked when FMGO attempts to reconnect. Then a message appears to Revert the record because changes can't be saved because the record is being used by someone else. (nobody else is in the record). When the user selects Revert (which is their only option), the whole found set of records is deleted. I might expect one record being affected by not a whole found set of records. There are not any cascading deletes that might affect this. Has anybody else experienced anything like this and were you able to resolve this issue? I have emphasized properly closing files, to avoid disconnected but this doesn't always happen with over 30 users.