All projects MUST be upgraded and recompiled after the installation of this Service Pack.Failure to do will result in conflicting database size messages. To force an upgrade, edit the Citect.ini file and set [CTEDIT] UPGRADE=1. Ensure that the Incremental Compile menu option is not checked, or set [CTEDIT] INCREMENTALCOMPILE=0.


The following files have been updated by this Service Pack.


















This Service Pack fixes the following problems:

* NCR 15381 - Citect layout saved.

Citect Editor, Explorer and Graphics Builder now save their window layout upon exit and restore it upon the next startup.

* NCR 15554 - A client/server connection is not re-established on Win2000.

A client/server connection is not re-established after a network failure when using NetBios over TCP/IP on Win2000 machines.

* NCR 15877 - Alarm Page may not display all requested alarm categories.

If there is a large number of comma separated alarm categories set to the alarm by using Cicode function AlarmSetInfo(), the alarm page may not display all of them.

* NCR 16110 - SQLGetField() does not display 'Text' data type fields.

When using the Cicode function SQLGetField(), fields of 'Text' data type will not be displayed.

* NCR 16482 - Maximise Citect Window.

Maximise doesn't work correctly when there is a taskbar on top.

* NCR 16532 - Scrolling to realtime on Windows 98 with a timezone negative of GMT.

Hitting the scroll to realtime button calls TrnSetTime with a value of zero for its time argument. This should cause the time to be set to the current time. Instead it is always set to "12:00:00 AM 31/12/1999". This problem only occurs if you are on Windows 98 and if your timezone is negative from the GMT, such as USA.

* NCR 16549 - ExportFileButton() and ExportClipButton() functions return incorrect data.

Values do not match up correctly to timestamps, and are not in the right order.

* NCR 16550 - When exporting millisecond trends, some timestamps and values are duplicated.

TrnExportCsv, TrnExportdbf, TrnExportClip, TrnExportDDE and _TrnExport all have this problem when using periodic trends.

* NCR 16551 - Yearly trend files do not work.

They cannot be written to, and newly created files cannot be read from.

* NCR 16552 - Trend History Files from versions earlier than 5.00

Trend History Files from versions earlier than 5.00 do not work. Trend data from these files will not get displayed on the screen.

* NCR 16563 - Cicode tasks may sleep indefinitely.

After the startup of Citect when Windows (OS) has run more than 49.7 days some Cicode tasks may not wake up for at least another 49.7 days.

* NCR 16566 - Wrong compile error generated when CiVBA inserted in expression fields.

The compile error "Operand expected" generated when the CiVBA keyword is found in an expression field such as the movement or scaling expressions of a dynamic object is not sufficiently specific.

* NCR 16572 - Trend Raw and Engineering scales are rounded down to the nearest integer.

The Zero and Full scales of Raw and Engineering values that contain decimal values will be rounded down to the nearest integer, which will cause the Trend values to lose precision.

* NCR 16578 - Mouse event not handled when window gains focus.

If the Citect runtime window has just come back into focus then left mouse events are not handled until the mouse has been moved.

* NCR 16582 - Citect Communication Express Wizard may fail.

On Windows 2000 with Service Pack 2 installations the Express Wizard will fail when attempting to edit an IO Device. The Express Wizard responds with "Unable to open 'units.dbf'" and exits after OK button is pressed.

* NCR 16638 - Editing and removing properties of nested genies.

When editing the properties of a base genie (i.e. a genie that does not contain another genie) the changes may not be reflected in any genies in which the base genie is nested.

* NCR 16724 - Potential Periodic Trend Historical Data overwrite.

When you Shutdown Citect and restart some time later, data corruption may occur in the Trend history files.

* NCR 16740 - The Decimal Separator in CTAPI output data is not localised.

The CTAPI uses hard coded symbol (.) for the separator of decimal number rather than using the decimal separator in Windows Regional Numbers setting.