Offline and Non-Offline Differences
Task Prefix
In Offline tasks the Task Prefix logic unit executes on the client. In non-Offline tasks it executes on the server.
Subforms
In Offline Rich Client tasks, the subforms are loaded and drawn after the logic in the parent task's Record Prefix logic unit is finished.
This means that:
-
When having a task subform:
-
In non-Offline Rich Client tasks, the Task Prefix logic unit of all subform tasks gets executed after the Task Prefix logic unit of the parent task. (This reduces the number of server requests and improves performance). Once the program is loaded, the Record Prefix logic unit of all the subform tasks are executed after the Record Prefix logic unit of the parent task.
-
In Offline Rich Client tasks, first the Task Prefix and Record Prefix logic units of the parent task are executed and then the Task Prefix and Record Prefix logic units of each subform task are executed one by one.
-
When evaluating an operation in the Task Prefix or Record Prefix logic units of the parent task that suspends the form load, such as a Verify operation, then:
-
In non-Offline Rich Client tasks, the subform will be drawn before that operation.
-
In Offline Rich Client tasks, the subform will be drawn after that operation.
.NET Assemblies
In non-Offline Rich Client programs, the server will take the third-party .NET assemblies from the CRR's .NET Assembly path and copy them to the client.
In Offline programs, third-party .NET assemblies defined in the CRR will not be downloaded to the client automatically. You should either install them on the client or use the ServerFileToClient function to copy the assembly to the client on initial startup.
Rich Client and Online Differences
