Software Customisation Reference Manual

Summary of Objects, Members and Methods : Object Type Details : SESSION Object
The LocationName member and Location() method imply the location to which the Session applies. This is normally the current location, except when Sessions at remote locations have been requested. In a non-Global project, these members and methods may be unavailable or unset.
Some ADMIN Sessions in a Global project may apply to another location's system database. This will be returned as part of the string returned by the Module() method, if relevant. Other ADMIN Sessions may actually be Global Daemon Sessions. This is returned as part of the string for the name member.
The Modified() method only applies to the current Session at the current location.
The Current(), Deferred(), Mode() and Status() methods will not be implemented for remote Sessions and will return an error.
The Location(), MDB(), User() and Module() methods are valid for remote Sessions.
It should be should be observed in using the MDB and USER objects returned by the MDB() and User() methods for a remote Session. Methods on these objects will access the currently open system database. Thus the appropriate location's system database should be opened (using the ADMINISTER SYSTEM command) before invoking methods on these remotely generated MDB and USER objects.

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo