Synergex.SynergyDE.synrnt 10.3.3030

This package has no dependencies.

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

-- You can now pass a dynamic array of structures through XSUBR
with Synergy .NET. [tr#36807]

-- The Synergy .NET runtime now logs licensing errors to the dbs
event log. Note that "unknown source" will be logged for a
ClickOnce deployment if Synergy is not installed on the target
machine. [tr#36857]

-- When an error occurs in the windowing routines (for example,
W_AREA) and it's called from a method, the error reporting now
unmangles the method name instead of reporting the mangled
method name. We added an optional parameter to the ERRMOD routine
that (when it's non-zero and the error routine is a method)
causes the method name to return unmangled. If the value is 0 or
the parameter is not passed, the mangled name is returned. This
also applies to %DBL$ERRMOD. [tr#34310]

-- Explicit and implicit Select AND optimization now occurs when
ORs are present but not optimized for OR (like the keys used by
the ORs are different or non-keys) or Where.In() on a non-key.
Previously, no optimization occurred even though a key on the AND
side of the tree could be optimized. For AND optimization,
Where.Keynum() is now only required to override OR/In optimization
with AND optimization of the specified key. Also, AND must be on
top of the expression tree with only ANDs present on one side for
AND optimization to occur. (See the entry for tr#36601 in
rel_dbl.) Setting DBG_SELECT now displays an "OR+AND (OR on top) -
optimization cancelled" message when AND is not at the top and
the entire expression cannot be optimized. [tr#36989]

-- The SORT statement has been updated to make better use of
memory. SORT now determines optimal memory usage to avoid
excessive intermediate I/O with an upper ceiling limit of 4 MB
on UNIX and 64 MB on Windows. You can adjust the upper ceiling
by setting the new environment variable SORTMEMMAX=<kilobytes>
(the number of kilobytes that SORT should not exceed). A
significant performance improvement may occur when sorting
large files (with very large and/or many records, including tens
of millions). You must unset the existing SORTMEM environment
variable to enable this feature; if SORTMEM is set, it will
override the optimal memory feature. The Select class, which
uses SORT on large selections using Orderby.Ascending and
Orderby.Descending, will also use this feature, as will remote
SORT over xfServer. [tr#37060]

-- With the 32-bit 10.3.3b Synergy .NET runtime, a Select with a
Where expression that had a comparison against a null string
or "" would not match on a blank. This has been corrected.
[tr#36867]

-- With the Synergy .NET runtime, SRUN licenses were not freed
when an appdomain was exited. This has been corrected. [tr#36887]

-- A Synergy .NET Windows Service application will no longer hang
when the service is stopped during execution of the .NET
Framework OnStop method. [tr#36889]

-- Examining variables for a Synergy .NET application in Visual
Studio sometimes caused an "Invalid variable" error. This has
been corrected. [tr#36921]

-- In rare cases, an error (e.g., BadDigitException) caused by a
Select statement would be detected by a later statement. This has
been corrected. [tr#37051]

-- In versions 10.3.3 through 10.3.3b of the Synergy .NET
runtime, trapping a generated error in an appdomain would cause
an error in the default appdomain instead of the appdomain that
generated the error. This has been corrected. [tr#37052]

-- In 10.3.3b, a Join using a tag field did not correctly match
against the tag when the joined files were accessed via xfServer.
In addition, using a Sparse object caused xfServer to crash.
These have been fixed. [tr#36924]

-- In 9.5.1 through 10.3.3b, LPQUE with DBLOPT #22 set failed to
spawn dblpq.bat when run under dbr.exe. This has been fixed.
[tr#37010]

-- On a READ or FIND where no positioning argument was specified
(key specification, POSITION:, ^FIRST, ^LAST, RFA:, etc.), a READ
still occurred and a "Key not same" error was generated. A new,
more appropriate $ERR_INVRD error ("Invalid READ, %s") is now
generated. [tr#32446]