You may carry out freezing and locking operations on either a MACRO server or at a study site. Each time you freeze or lock an item, a freeze/lock message is created. During data transfer, these messages are transferred between the server and the relevant sites.
On a server, you will not see the effects of freeze/lock messages from a site until the subject data files have been imported into the server's database.
At a site, you will see the effects of freeze/lock messages from the server as soon as data transfer has finished.
A full audit trail of freeze/lock operations can be viewed in the Freeze/Lock History Browser.
Freeze/lock messages created on a MACRO server may be refused at the site if they conflict with data changes at the site. If a freeze/lock message is refused, the operation will be rolled back on the server, leaving the item on the server in the state it was in before the freeze/lock operation took place.
In the case of conflicting freeze/lock operations, actions at a site always take precedence over those performed on the server.
For example, if you freeze or lock a question, eForm or visit for a particular subject on the server, and someone else has made changes to that question, eForm or visit at the site, the freeze/lock operation from the server will be refused at the site, and will be rolled back on the server. When the data from the site arrives at the server, the items will be updated to match the state they are in at the site.
Viewing the Freeze Lock History Browser