1. Title to and ownership of the software and documentation shall remain with the Contractor.
2. Use of the software and documentation shall be limited to the facility for which it is acquired.
3. The Government shall not provide or otherwise make available the software or documentation, or any portion thereof, in any form, to any third party without the prior written approval of the Contractor. Third parties do not include prime contractors, subcontractors and agents of the Government who have the Government's permission to use the licensed software and documentation at the facility, and who have agreed to use the licensed software and documentation only in accordance with these restrictions. This provision does not limit the right of the Government to use software, documentation, or information therein, which the Government has or may obtain without restrictions.
4. The Government shall have the right to use the computer software and documentation with the computer for which it is acquired at any other facility to which that computer may be transferred; to use the computer software and documentation with a backup computer when the primary computer is inoperative; to copy computer programs for safekeeping (archives) or backup purposes; and to modify the software and documentation or combine it with other software. Provided that the unmodified portions shall remain subject to these restrictions.

The most current list can be obtained from the InterSystems Website.

Users should check this list periodically to obtain the latest information on issues that may have an effect on the operation of their site.

• Phone:  +1  617  621-0700
• Fax:  +1  617  734-9391
• Email:  support@intersystems.com

Formerly, selecting one of these nested sub-properties would cause invalid SQL to be generated and thus cause a page error upon clicking the Search button.

This change causes the Message Browser to generate SQL arrow ('->')syntax for references to such sub-properties, resulting in SQL that is valid if the sub-property belongs to a persistent class type.

This change also generates a valid SQL 'AS' name for the column displaying the sub-property values. It does this whether the sub-property is named using a dot separator or if it is named using an arrow separator entered by hand.

This change detects the errors associated with this situation and attempts to recover from it. It also attempts to fix itself when daemon creation fails.

It also fixes issues with long string SET command recovery across ECP. If the server or connection fails in the middle of a SET involving a long string, the assignment may fail with <NETWORK> error or the SET may be dropped altogether.

• The ECP server is a different endianness than the application server;
• There is a SET in the process of being propagated to the client;
• The SET involves a non-compact Unicode string;
• The block that the SET will modify has arrived at the client;

However, the code that then switched this page into this namespace was not using the value passed in, but the value from the %session.RunNamespace which was incorrect at this point. This change uses the correct value.

It appears when you have password authentication this is not a problem, but it does effect systems that are using the Unknownuser.

Users can copy the [LAT] section from an existing cache.cpf file into the new lat.ini file or you can enter the information with a text editor.

This change implements the correct behavior.

Thus for every failed login attempt, Caché would hang 1 second longer, until a valid login attempt would occur. On an account that could generate hundreds of invalid login attempts, the hang could last a long time. The code has been updated to hang for a maximum of 20 seconds.