Each TerraExplorer object and Information tree group has a text string assigned to it, this information is called the Client data, and it is saved in the TerraExplorer FLY file. The client data is used for saving attribute information about a specific group or object and for saving information relating to your application.
To avoid conflicts between TerraExplorer and different client applications, the client data is arranged in Namespaces. Each Namespace is defined by a string identifier. You should define the Namespace identifier from which to store or retrieve data. For example, you can use “MyApplication” as an identifier for your information.
For Groups, you can access the client data using the IInformationTree5::SetClientDataEx() and IInformationTree5::GetClientDataEx() IInformationTree5::GetClientDataEx()methods. You can write your own custom string, or update the current one.
Note: The SetClientData and GetClientData methods store the text string in the global Namespace. It's recommended to use the extended methods above. You can access the global namespace by passing an empty string for the Namespace identifier.
For Objects, any object derived from ITerraExplorerObject5, has a ClientDataEx Property to which you can write, and from which you can read.
TerraExplorer stores feature layers attribute data as an XML in a standard format as described in ITerraExplorerObject5::ClientDataEx property. When using the query tool to select this object in TerraExplorer, this information is displayed in a special container. Be aware that tampering with this information may result in functionality loss.
Note: The ClientData property stores the text string in the global NameSpace. It is recommended to use the extended property above. You can access the global namespace by passing an empty string for the Namespace identifier.
See: “Working with Client Data” for a VBScript example code.