Does Set Field on Global Fields Need to be Committed?
"In FileMaker Pro 7, the 'Set Field' script step has been modified so that it makes the record active and keeps it active when necessary (like in the case of modifying any non-global fields) and possible. The record will be made active but no field(s) will be made active. This means that a series of 'Set Field' commands will act on the record without actually locking the record. Furthermore this also means that normal record-level validation will take place once the record is exited or committed."
Does this mean that Set Field used on global fields in non-active layouts do _not_ need to be committed? Recall that global fields for guest users are never sent back to the host database.