A way to reduce network traffic when using 4D Open is to cache the structure on the 4D Open local machine. By caching the structure, you are storing on the local machine structure information that in normal practice the local machine would have to ask for from the remote 4D Open machine.

If you do decide to cache the structure, you must make sure that the structure is not in a state of constant change. Any changes made to a structure after a caching session is started by 4D Open will not be reflected within the 4D Open connection. Each caching session lasts as long as the 4D Open session is active. This means that each time a 4D Open session is started, the structure is cached on the local machine.

In order to perform the caching, two 4D Open commands need to be called: OP Set option, which tells 4D Open that you can cache the structure, and OP Cache structure, which actually will cache the structure.

Example:
$ErrCode:= OP Set option (3;1)
$ErrCode:= OP Cache structure (vConnectionID;1)