If the user enters some data into a record and does not commit the changes before they close up their laptop, those changes might not be saved to the database and the data could be lost. Much of the time, user actions automatically commit the data, changing layouts, closing the database window, changing records, clicking the layout background all commit the current record. So this might only happen if they close their laptop immediately after entering some data.
OK, so if they type something in a field and leave the cursor there, it would NOT be commited, but if they select an item from a popup/checkbox/radio button, etc, it would be commited, correct?
If the data is not commited, is the worst case that it would just loose that particular data, or could it potentially corrupt the host DB?
Data entered by interaction with a layout control such as a radio button or pop up is also not committed until one of the actions that I described commits the record.
I can't see any way that this would corrupt the hosted file--especially if it is hosted via server and not via FileMaker Pro.
Worst case scenario would be a loss of data from the layout's current record and any modifications to related records such as rows of data in a portal if that data was not committed.