If your database uses triggers and plug-in areas, the following information can be very useful.
Let us assume that, in a form, you associate a 4D Write area to a field. If you selected the database event "On Saving an Existing Record" and defined a trigger that uses that event, the following behavior will take place:
Each time the form is loaded, the loading of the 4D Write area will set the status of the record to "modified" so, even if the contents of the plug-in area (or the contents of any field) are not modified, the trigger will execute.
If you want to work around that standard behavior, you can use a 4D Write area that is not saved into a field and initialize/save it when the form is loaded/unloaded.