1405.6.1 |
XTREE/ATE (client-side) bug fix: the row update optimization was creating a bogus extra row when using XTROP_REPLACE and the first row being loaded didn't match the existing first row. Problem has been present for a long time, but most likely only became visible after updating both the server and client beyond 6.1.1400.3. |
1405.6.2 |
INFLD/ATE (server-side) bug fix: in some cases, fields without an explicit MAXCHARS specification weren't returning any data. Bug introduced in 1405.3. |
1405.5 |
XTREE diagnostic feature: defining the environment variable XTRNOOPT1=1 on the server side will disable a particular row optimization; for testing purposes. |
1405.4 |
EVENTWAIT bug fix: Was using excessive CPU time when TIMER option active. |
1405.3 |
INFLD / ATE bug fix: The maximum field length was being artificially limited to 456 bytes when in ATE mode. |
1405.2 |
PDFX bug fix: Save.Type,3, delete after email, was causing various problems when used with Email.Type 4+. At best it was causing the process to wait a long time before giving up, and in the case where the driver was running in background, such as on an ATSD server, it was simply hanging indefinitely. With this patch, it works as expected with Email.Type,4. For Types 5 and 6, the delete option is just ignored, since it can't be coordinated with the async MAPI interface to the email client. |
1405.1.1 |
ATSD fix: The FORCE command, and some SEND command variations, were failing to work on jobs running under ATSD. Note that even with the fix, FORCE will not work properly if the target is in an ATE client-side GUI operation. |
1405.1.2 |
Runtime bug fix: setting a dynamic overlay variable to a zero-extent array no longer generates a subscript out of range error. |
1405.1.3 |
XTREE refinements: clean up a few minor internal issues related to cases where you are rapidly entering/exiting a tree, such as with ExitChars and SelChgExit. |
1405.1.4 |
PDFX bug fixes/refinements: (1) The waiting dialog (added in 6.1.1401.0) was causing the session to hang when running PDFX on an ATSD server under certain Windows Server versions. Now when the file takes more than 5 seconds to appear in the directory, it starts displaying a status message on the bottom status line, and waits up to 40 seconds before giving up. For local Windows operation, it uses the session status line, rather than the bottom status line, to display the waiting status message. (2) Specifying a file in an Email.AttachFile statement that does not exist was in some cases causing the session to crash. |
1405.1.5 |
FTP2.SBR / ASHNET.DLL 1.7(147) refinement: you can now override the default timeout for FTP2.SBR (60 seconds) by defining the environment variable FTP2TIMEOUT as the desired timeout in seconds, e.g. .SETENV FTP2TIMEOUT=10. Note that this is implemented entirely in ASHNET.DLL. |
1405.0.1 |
Improve File Auto-Close Behavior with respect to SBXs. |
1405.0.2 |
Revisions to ASFLAG behavior. Previously, the ASFLAG options were cleared at the start of each SBX. They are now passed from the current program (parent) to the SBX (child). As before, flags set within the SBX do not affect the caller, except for AF_EXITSBX and AF_SETCTRLC. |
1405.0.3 |
Eliminate the AF_SQLPERSIST flag in ASFLAG.SBR introduced in 6.1.1404. |
1405.0.4 |
Print filter bug fix: the $PREFIX and $SUFFIX macros (introduced in 6.1.1398) were failing to get set by the prefix and suffix parameters in the SPOOL or EZSPL subroutine call. Values passed as parameters in the XCALL should override any corresponding settings in the printer init file. |
1405.0.5 |
Windows Print filter bug fix: changes to the copies and switches within a print filter (under Windows) were not having the desired effect if the print filter returned with STS=1 (to proceed with printing). |
1405.0.5 |
CGI bug fix: the parameter passed to the CGIOP_STDOUT call was being truncated at 4095 bytes. |