Synergex.SynergyDE.synrnt 10.3.3020

This package has no dependencies.

For runtime fixes and enhancements specific to traditional
Synergy, see rel_dbl.txt.  

-- SORT/MERGE did not generate an error when one of the key fields
did not belong to the specified record. This has been fixed to
generate a BADKEY error. [tr#34813]

-- (Windows, UNIX) Reading and writing file text in an ISAM file
has now been coordinated between processes. Changes by one process
are now immediately available to another process. [tr#36667]

-- GetCTInfo from an AlphaEnumerator class no longer returns an
invalid CTInfo object if the Select's Where does not specify
change tracking. Now a ^NULL object is returned. [tr#35534]

-- A segmentation fault no longer occurs on a Select that includes
a Where expression containing OR operators referencing the same
key field or a Where.In. Typically, this condition was occurring
when the Where.In (or the set of OR operations) occurred along
with a minimum of two additional AND operations. [tr#36825]

-- Using Contains within an On expression no longer causes an
$ERR_INVOPER error ("CONTAINS operator left operand requires field
reference"). [tr#36816]

-- LeftJoins in a multi-table join that evaluate to NULL no longer
terminate the further evaluation of additional joins on the same
JoinSelect. [tr#36804]

-- A JoinSelect using remote files over xfServer now returns the
correct data for all joined rows when SCSPREFETCH is set.
[tr#36783]

-- Previously, S_BLD would fail with an error (BIGNUM) when an i8
with a large number was passed to a %d format string on a 32-bit
platform. This has been corrected. [tr#36794]

-- With Synergy .NET, an AccessViolationException would sometimes
occur during garbage collection after several instances of
JoinSelect. This has been corrected. [tr#36697]

-- With Synergy .NET, displaying to a channel that was not open
caused a segmentation fault. This has been corrected. The runtime
now reports that the channel is not open. [tr#36819]

-- A Select Where expression with optimized .OR. operations (all
.OR. operations are against the same key) or a Where.In (when
optimized) now returns selected records when the first (leftmost)
condition is false based on the existing data. [tr#36841]

-- Previously, in some rare cases a Select with a large Where
expression (around 70 operations or more) would fail to return
all records that matched the criteria or would cause some other
unexpected results. This has been corrected. [tr#36843]