InTouch 7.11 Patch 06

InTouch^® 7.11 Patch 06 ReadMe

This document provides information regarding bugs fixed in this patch and other known issues.

· It is strongly recommended that you exit all FactorySuite^® programs, including the .exe files and services, before installing this patch.

· If a DAServer is going to be installed on the same node with InTouch 7.11, then InTouch 7.11 and all of its patches MUST BE installed prior to installing the DAServer.
If the DAServer is already installed, it will need to be reinstalled after installing this patch.

· This InTouch 7.11 Patch 06 Build has primarily been tested on:
* Windows XP Professional with SP1 and MDAC 2.70
* Windows 2000 Professional with SP3 and MDAC 2.60
* Windows NT 4.0 SP6a and MDAC 2.60
* Internet Explorer 6.0

Resolved Issues

The following bugs were fixed for this patch release. Please click on the bug number for a more detailed description of the problem.

L00006838 Check boxes for the vertical and horizontal scrollbars of the distributed alarms display disappeared.

L00007809 An incorrect title for the Keypad dialog box is displayed after the ChangePassword() function is called; the "Enter new password" title is always displayed, even when the old password is entered.

L00010999 $system.AlarmUserDefStr=$operator; is not working as expected. In the OperatorName column and User3 column, the AlarmDetail entries are not the same.

L00011533 A halo or a square around an object (link) stays visible when the window is larger than the current resolution's.

L00011635 The Alarm Buffer Size in the Alarm Distributed Object cannot be set.

L00011648 The InTouch print-to-text file does not wrap around nor line-break correctly.

L00011659 The AlarmComment field for the Message tags is missing for the DBDump/DBLoad.

L00011719 The DialogValueEntry() function does not display properly in a multi-monitor environment.

L00011721 The DialogStringEntry() function does not display properly in a multi-monitor environment.

L00011757 The 16-Pen Trend loses data when another window is opened.

L00011790 The SQLInsertPrepare and SQLInsertExecute do not insert NULL into the database. An error message, "-1: Type mismatch. >>Error >>Executing SQLInsertExecute," is displayed.

L00011825 The SQLSetParamChar() function does not work properly in the new SQL ACCESS.

L00011927 The Alarm Query Favorite was overwritten by entries for the default query.

L00012046 The Distributed History queries to InSQL version 8.0 are not properly formed when used with the international Operating Systems.

L00012230 The WindowViewer crashes if the 16-Pen Trend is used without any tags assigned to the pens.

L00012271 The Dialog Modal property of All Scripts suddenly does not work, after any error comes in, while it is in Validation process.

L00012354 The Alarm Printer should not print "state" information for events.

L00012369 WindowMaker - selecting an item through a mouse click forces the object to jump up and over by one pixel.

L00012425 It takes a long time for the AlarmDBView Control to get populated with data, if the database contains a large number of records.

L00012439 Problems arise when creating a new application with certain Japanese characters.

L00012497 When used in a button with other scripts, the Dialogvalueentry() causes InTouch to stop responding.

L00012500 The Tab order is not in proper sequence for the Cross Reference Utility dialog box.

L00012535 WindowMaker will crash when converting an application containing Intrack ActiveX controls.

L00012554 An abnormality occurs when interlocking a value entry based on specified tag limits.

L00012646 The Alt-Q Shortcut key, in the Cross Reference Search Criteria dialog box, is assigned to the "Checkbox usage in QuickFunction" and the option button "Quick Functions."

L00012770 When run on Windows 2000 SP2/3, it takes a long time for WindowMaker to save windows to a file server/network location. The same windows are saved quickly when WindowMaker is run on Windows NT4.0 SP6a.

L00012839 The "Analog Tagname Display with Tagname Text" wizard does not display a tagname and value properly, if the tagname contains the number "0" (zero).

L00012979 Changing the customized palette color to Unack Alarm, for any priority, stops the system from responding.

L00013425 A WWHeap error message appears when converting a script, because the Access Names dialog box is displayed as modal-less.

L00013652 The "Cannot Create Tag Limit Exceeds" dialog box is not modal when creating the Super tag instance, if the limit of the allowed number of tags (61405) is exceeded.

L00013664 There is a hard-coded string in the WWkeypad module.

L00013834 The X or Y location of a window changes, when the width or height of the window is manually reduced.

L00013856 When entering an invalid, floating-point value (for example, entering a comma instead of a decimal point), the error-message box window shown then is not modal. This issue occurs in the German version of the application.

L00014081 Hex numbers are treated as tags in script editing, when they are concatenated with a close parenthesis, ")", without spaces. For example, (0x010 + 0x0A0).

L00014244 An additional validation is required for the Duration and Interval tags of the HISTDATA object.

L00014270 The WWALMDB misses the first event that occurs when WindowViewer is disconnected from the database.

L00014399 The error message, "Cannot open tagname.x," is displayed after windows containing previously exported Clock wizards, are imported.

L00014425 The 3-D pipes (default size) from Symbol Factory have their size changed after converting to InTouch7.11.

L00014652 There is an issue with the rounding off of the min/max values for the EU fields and the lo/hi limits. The two are not rounding off to the same numbers as they should, in accordance with the IEEE standards for the floating precision numbers.

L00014653 The 16-Pen Trend does not repaint correctly when the window is locked up (Ctrl+Alt+Del).

L00015072 The DialogValueEntry allows NULL to be entered, and then translates it into zero.

L00015121 If the changes of the tagname value are smaller than the update rate, the trend displays a min/max value box until the tagname value changes again.

L00015315 The Purge/Archive utility's partial purge function fails; however, the utility can purge the whole database in 4 (four) minutes.

L00015361 The visibility animation link and the discrete-value display animation link have the ON button on the left and the OFF button on the right. The color-fill animation link, however, has the locations of the buttons reversed.

L00015540 The condition script's "while loop" does not work correctly.

L00015569 WindowViewer crashes on open, after the application has had some minor window changes; a tag is also deleted.

L00015617 The 16-Pen Trend crashes in tdatasrc.exe.

L00015746 The timestamp of the I/O tags is not updated properly, if the change is triggered locally through a user input. This results in the data being viewed as "Out-of-date" by InSQL. The same occurrence happens when the tag is poked from another source.

L00015819 The Purge/Archive utility fails to shrink the database after the purge operation is completed.

L00015936 If an ActiveX Control is active, a frame is shown around this control.

L00015939 When using update use counts, the WindowMaker crashes and a Dr. Watson message is displayed.

L00015942 The Polygon is changing when a user is switching between WindowMaker and WindowViewer.

L00015983 The 16-Pen Trend shows an extra, long vertical line, where there should just be a single point; and, the pen thickness increases at the left of the screen.

L00015992 After implementing the hot fix from CR#L00014652, alarms are now being generated when tag.value = tag.HiLimit, or tag.value = tag.MaxEU.

L00016141 WWLogger consumes 100% of the CPU time. This is always initiated by an incomplete line, in the WWLogger, that has garbled characters.

L00016238 Using the TRUNC function to truncate real numbers gives an incorrect result.

L00016389 Clicking on the Cancel button will undo the animation link.

L00016427 The new return string feature of QuickFunction in Patch 5a causes memory leak.

L00016440 Error messages are logged when a 16-Pen Trend scooter is pasted onto a window, and when a window containing a 16-Pen Trend scooter is opened.

L00016548 There are corrupted fonts in the Recipe dialog boxes when the Japanese local settings are used.

L00016751 ptSetPenEx causes the configured pen color to change, and the width to go to the default value of one pixel.

Detailed Description

L00006838 Check boxes for the vertical and horizontal scrollbars of the distributed alarms display disappeared.

Problem:
Check boxes for the vertical scrollbar and horizontal scrollbar of the distributed alarms display disappeared in Patch01 onwards.

Problem:
"Enter new password" is the title for the Keypad dialog box displayed when clicking on the button for "Old Password," "New Password," or "Verify New Password."

L00010999 $system.AlarmUserDefStr=$operator; is not working as expected. In the OperatorName column and User3 column, the AlarmDetail entries are not the same.

Problem:
The issue occurs when an alarm record is acknowledged, and only 3 (three) parameters, ACK-OPERATOR NAME, ACK-COMMENT, and ACK-OPERATOR NODE NAME, are changed.

Now, in the detailed database, the user-defined fields are populated.

L00011533 A halo or a square around an object (link) stays visible when the window is larger than the current resolution's.

Problem:
When the window is larger than the current resolution's, a halo or a square around an object (link) stays visible.

L00011635 The Alarm Buffer Size in the Alarm Distributed Object cannot be set.

Problem:
The Alarm Buffer Size in the Alarm Distributed Object cannot be set.
The size of the buffer must be the same as the setting in the \Special\Configure\Alarms\general\Alarm Buffer Size.

L00011648 The InTouch print-to-text file does not wrap around nor line-break correctly.

Problem:
Print to text file:

The line break does not always work.
The file contains special characters in the text.
The wrap-around text function does not work; some information might be cut off.

To resolve the problem, the following features have been added:

A new dialog box to specify output to printer or to text file.
A selection for a printer.
A selection for text file.

L00011659 The AlarmComment field for the Message tags is missing for the DBDump/DBLoad.

Problem:
The AlarmComment field was introduced for Message tags. This field also needs to be addressed in the DBLoad and DBDump functions for Memory and IO Message tags. The Indirect Message tags should also support this new dot field.

L00011719 The DialogValueEntry() function does not display properly in a multi-monitor environment.

Problem:
The issue is that when this function is called, the dialog box is shown split between the monitors and cannot be moved or resized to gain access.
All the other dialog boxes on the system show up on the first monitor, or are moveable as expected.

When the DialogValueEntry() function is called, the dialog box is seen split between the monitors because it is not coded to work on a multi-monitor environment.

L00011721 The DialogStringEntry() function does not display properly in a multi-monitor environment.

Problem:
The DialogStringentry() function is shown stretched across multiple monitors in a multi-monitor environment, and it cannot be moved.

L00011757 The 16-Pen Trend loses data when another window is opened.

Problem:
When the 16-Pen Trend is used in the Real Time configuration, data will be seen disappearing when a window is opened over the trend and then closed.

L00011790 The SQLInsertPrepare and SQLInsertExecute do not insert NULL into the database. An error message, "-1: Type mismatch. >>Error >>Executing SQLInsertExecute," is displayed.

Problem:
SQLInsertPrepare and SQLInsertExecute send data to a database, and if that data contains a NULL or an empty string, an error message will be generated in the WWLogger and no entries are made in the database. But, if the exact same data is inserted using just SQLInsert, a NULL or an empty string is inserted with no errors.

L00011825 The SQLSetParamChar() function does not work properly in the new SQL ACCESS.

Problem:
The same script worked in the old SQL ACCESS, but it does not work properly in the new version.

L00011927 The Alarm Query Favorite was overwritten by entries for the default query.

Problem:
If a "query favorite" is entered to the DAO and then the queries are sorted by name, the new query is shown at the top. When the window is closed, then reopened, and the object is right-clicked on to view the query favorites, the query that has just been entered is gone. There are now 2 (two) entries for the default query.

L00012046 The Distributed History queries to InSQL version 8.0 are not properly formed when used with the international Operating Systems.

Problem:
When using InSQL Server running on the German version of Windows and SQL Server 2000, the queries that are formed by InTouch's Distributed History engine are always formatted as "mm/dd/yyyy" format, regardless of the localized regional settings. If the requested days are between the 13th and 31st of the month, the data is retrieved correctly. However, if the days are between the 1st and the 12th, the day portion is treated as if it were the month.

For example, a query from 1/11/2003 thru 1/12/2003 returns data from November 1 through December 1, 2003, rather than from January 11 through January 12, 2003.

L00012230 The WindowViewer crashes if the 16-Pen Trend is used without any tags assigned to the pens.

Problem:
This is a follow-up of CR#L00006574: The WindowViewer crashes if the 16-Pen Trend is used without any tags assigned to the pens.

L00012271 The Dialog Modal property of All Scripts suddenly does not work, after any error comes in, while it is in Validation process.

Problem:
Open any Script, for example the Application Script dialog box, and write a script, for example, (Tag1 = Tag2;). In the example, Tag1 and Tag2 are not defined, therefore an error message, "Define Tag1" will be displayed. Click on the Cancel button and without closing the Script dialog box, click on the File menu or any where, even on the Runtime. These activities can be performed, even though they are not allowable.

This means that the Modal property of the Script dialog box is now gone.

L00012354 The Alarm Printer should not print "state" information for events.

Problem:
The Alarm Printer will print "alarm state" information (UNACK_RTN) for the event records. In order to be consistent with the alarm displays, logger, and so on, events should not display any type of alarm-state information.

L00012369 WindowMaker - selecting an item through a mouse click forces the object to jump up and over by one pixel.

Problem:
If the grid is turned off (through the "View" toolbar), and in WindowMaker an object is selected on the window, the object will jump by one pixel, up, and to the left. If on the other hand, you click around and the object is not moved, the subsequent selections of the object do not cause this jump.

L00012425 It takes a long time for the AlarmDBView Control to get populated with data, if the database contains a large number of records.

Problem:
If the WWALMDB database has 200,000 or more records in it and the AlarmDBView Control is opened to query the alarms from the last 5 (five) minutes, even if there are no records returned, it takes 110 to 180 seconds (2-3 minutes) to have the AlarmDBView populated.
Running the same query from the Query Analyzer also results in the same delay. The longest delay is when the SQL Server is on another node.

To resolve the problem, the following steps need to be taken:

Provide the configuration parameter Top Max Records in AlterWWALMDB.exe. This will help you in configuring the Top Max Records (which is basically a row count) for a fast alarm-records retrieval. By default, the value of Top Max Records is 1000.
Change the CHAR data types of fields, which are above 4 (four) bytes, into VARCHAR type for better performance.

For the existing Consolidated mode database:

Option 1: Change the CHAR data type to VARCHAR.

Archive the database by using the "Purge All" feature from the Purge/Archive utility.

Create the Consolidated mode database again by using the Alarm DB Logger Manager utility.

Restore the data using the Alarm DB Restore utility. This will update the database with the latest changes. (Do not select the Recreate Tables check box option.)

Configure the Top Max Records field in AlterWWALMDB.exe as explained in the "Configuring the Top Max Records field in AlterWWALMDB.exe" section.

Option 2: Keep the CHAR data type.

Configure the Top Max Records field in AlterWWALMDB.exe as explained in the "Configuring the Top Max Records field in AlterWWALMDB.exe" section.

For the newly created Consolidated mode database:
Configure the Top Max Records field in AlterWWALMDB.exe as explained in the "Configuring the Top Max Records field in AlterWWALMDB.exe" section.

About the Top Max Records field in AlterWWALMDB.exe
The Top Max Records field in AlterWWALMDB.exe is provided for configuring the Top Max Records (which is basically a row count) for a fast alarm-records retrieval. By default, the value of Top Max Records is 1000.
For example, if you want to see the latest last-minute, or last-15-minute, or last-one-hour, or last-one-week records, then it is preferable to set the Top Max Records configuration parameter, using AlterWWALMDB.exe, to 1000 or below 1000. It depends on how many records you would like to view on AlarmView OCX Control and how many records are present in the WWALMDB database.

Configuring the Top Max Records field in AlterWWALMDB.exe

Double-click on the shortcut Programs\Wonderware FactorySuite\InTouch\Alarm DB Alter, or run AlterWWALMDB.exe in the InTouch folder.
Enter the server name, user name, password, and Top Max Records fields.
Test the connection by clicking the Test Connection button.
Click Alter Database button to update views.

Notes:

Every time, after modifying this configurable parameter, you have to click on the Test Connection button for initialization and connection; then click the Alter Database button to update the views.
Preferably, keep the Top Max Records configurable parameter as low as possible for a fast alarm-data retrieval.

L00012439 Problems arise when creating a new application with certain Japanese characters.

Problem:
Problems occur when creating a new application with certain Japanese characters; the characters are converted into different characters and the application is not opened.

L00012497 When used in a button with other scripts, the Dialogvalueentry() causes InTouch to stop responding.

Problem:
If the function is used in an on-key down script, and there is something in the on-key, in the up part of the script, InTouch will lock up. The lock-up is from a possible Windows focus issue.

L00012500 The Tab order is not in proper sequence for the Cross Reference Utility dialog box.

Problem:
The tab order for the Cross Reference Utility dialog box is not in a proper sequence.

L00012535 WindowMaker will crash when converting an application containing Intrack ActiveX controls.

Problem:
Converting an application containing Intrack activeX controls will crash WindowMaker.

L00012554 An abnormality occurs when interlocking a value entry based on specified tag limits.

Problem:
An abnormality occurs when interlocking the value entry based on specified tag limits. Data entry should be interlocked based on limits entered for the tag.

L00012646 The Alt-Q Shortcut key, in the Cross Reference Search Criteria dialog box, is assigned to the "Checkbox usage in QuickFunction" and the option button "Quick Functions."

Problem:
The Alt-Q Shortcut key, in the Cross Reference Search Criteria dialog box, is assigned to the "Checkbox usage in QuickFunction" and the option button "Quick Functions." There should be one Shortcut key for each.

Problem:
The WindowMaker open/save windows function is slow over the network run on Windows 2000; the same windows can be opened/saved quickly by the WindowMaker run on Windows NT4.0 SP6a.

The problem seems to be mainly with objects created using Symbol Factory or the AutoCAD DXF wizard, that is, objects consisting of many "pieces" from Silent Partner. For example, if the pump cell (located in the upper-left part of the window) is copied to another window and duplicated many times over, the window save progress is slow. In the process, the pump is first broken apart and after that the top symbol; this is because the window is composed of many objects, even though its size is not large.

L00012839 The "Analog Tagname Display with Tagname Text" wizard does not display a tagname and value properly, if the tagname contains the number "0" (zero).

Problem:
The "Analog Tagname Display with Tagname Text" wizard shows the following:

ITag121 = 0.00

It seems that WindowViewer incorrectly begins displaying value when it sees the first "0" in the wizard; the first zero, in this case, is part of the tagname.

L00012979 Changing the customized palette color to Unack Alarm, for any priority, stops the system from responding.

Problem:
When the customized palette color is changed to Unack Alarm, the system stops responding.

L00013425 A WWHeap error message appears when converting a script, because the Access Names dialog box is displayed as modal-less.

Problem:
The Access Name dialog box is displayed as modal-less when the script is converted to remote. If in the Script Editor, a click is performed outside the Access Name dialog box, the Access Name dialog box disappears; then, when the CANCEL or CONVERT button is clicked on in the Script Editor dialog box, the Script Editor dialog box is closed. If an Access Name is added, a WWHeap error message will be generated.

L00013652 The "Cannot Create Tag Limit Exceeds" dialog box is not modal when creating the Super tag instance, if the limit of the allowed number of tags (61405) is exceeded.

Problem:
When the allowed tag limit is exceeded, a message box "Limit exceeds the allowed number of tags" will appear. If you click outside the message box and close the tag dictionary, the WindowMaker cannot be closed. To close it, the Operating System will have to be shut down.

L00013664 There is a hard-coded string in the WWkeypad module.

Problem:
When a wrong password is typed in using the ChangePassword() script function, an error message in English appears. This message is hard-coded; there are other dialog boxes that have the same problem.

L00013834 The X or Y location of a window changes, when the width or height of the window is manually reduced.

Problem:
Reducing the width and height of a window manually will result in the X or Y location of the window being changed.

Problem:
When an invalid, floating-point value is entered, the error message box window that is shown then is not modal. This is an issue that occurs in the German version of the application.

L00014081 Hex numbers are treated as tags in script editing, when they are concatenated with a close parenthesis, ")", without spaces. For example, (0x010 + 0x0A0).

Problem:
Hex numbers are treated as tags in script editing, when they are concatenated with a close parenthesis, ")", without spaces. For example, (0x010 + 0x0A0). A warning dialog box "Cannot use numeric format in tagnames," is displayed.

L00014244 An additional validation is required for the Duration and Interval tags of the HISTDATA object.

Problem:
If invalid data is placed in the Interval or Duration tags and then the HistData is used to create a file with that information, a file with the same entry will be repeatedly generated; the files will keep on growing, causing the PC to fail because the hard disk runs out-of-space.

Note: It is recommended that the value of the HDWDuration is set not greater than the width of the Historical Trend. The .csv file will be very large if the HDWDuration is too large and the HDWInterval is too small. The minimum values for these 2 (two) fields are 10 milliseconds.

L00014270 The WWALMDB misses the first event that occurrs when WindowViewer is disconnected from the database.

Problem:
The first event that occurrs when the SQL Server is disconnected (that is, MSSQLServer service stopped) does not make it into the WWALMDB. There will be an entry for the missed event reported by the WWalmlogger, and it is posted in the WWLogger as "Logging events failed."

L00014399 The error message, "Cannot open tagname.x," is displayed after windows containing previously exported Clock wizards, are imported.

Problem:
When a window containing a Clock wizard is exported to the directory, the same window cannot be imported into a new application. An error "Cannot open c:\...... tagname.x". will be displayed.
This seems to occur only with windows containing Clock wizards which have been exported. The same window can be imported directly from one application to another without any problems.

L00014425 The 3-D pipes (default size) from Symbol Factory have their size changed after converting to InTouch 7.11.

Problem:
Converting an application developed using InTouch 7.1 Patch08 to InTouch 7.11 Patch04, results in Symbol Factory's 3-D-pipe objects having their dimension changed.

Different patches of InTouch 7.1 and InTouch 7.11 call Wizard_Size. To convert an application, which has Symbol Factory, from an older version to InTouch 7.11 Patch 06 without having the Symbol Factory size changed, follow the guide for the conversion as described for the following InTouch versions and patches:

Converting from InTouch 7.1 Patches 01 through 07 to InTouch 7.11 Patch 06: Do nothing.
Converting from InTouch 7.1 Patch 08 to InTouch 7.11 Patch 06: Add this line: CallWizardSize = 1 to InTouch.ini file.
Converting from InTouch 7.11 Patches 01 and 02 to InTouch 7.11 Patch 06: Do nothing.
Converting from InTouch 7.11 Patches 03 and 04 to InTouch 7.11 Patch 06: Add this line: CallWizardSize = 1 to InTouch.ini file.
Converting from InTouch 7.11 Patch 05 to InTouch 7.11 Patch 06: Do nothing.

Problem:
If the min/max values for the EU fields and the lo/hi limits, for a memory real or IOReal tag, are set, there are differences between the two; they are not rounding off to the same numbers as they should.

L00014653 The 16-Pen Trend does not repaint correctly when the window is locked up (Ctrl+Alt+Del).

Problem:
When a window is locked up (Ctrl+Alt+Del), the 16-Pen Trend does not repaint correctly. The trend background should be displayed, not the window background.

L00015072 The DialogValueEntry allows NULL to be entered, and then translates it into zero.

Problem:
The DialogValueEntry allows NULL to be entered, and then translates it into zero.
If the value is removed from the dialog box or a space is entered, and then 'OK' is selected, the DialogValueEntry passes a zero to the Integer tag associated with the function call. This should not be allowed, and an error message stating that the value entered is not within the range specified should be displayed.

L00015121 If the changes of the tagname value are smaller than the update rate, the trend displays a min/max value box until the tagname value changes again.

Problem:
If the changes of the tagname value are slower than 1 (one) second (= the update rate), everything seems to be okay. However, if the value is set to 1 (one) and then switched to 0 (zero) and back to 1 (one) during a time interval lower than the update rate (less than one second in this case), the trend displays a min/max value box until the tagname value changes again, even if the real value of the tagname value is constant (the minimum value per pixel is the same as the maximum value). On the classic Real-Time trend, one-second samples of the discrete tagname value can be seen.

There are "boxes" of the min/max values which also fill up the area where a tagname value does not exist. Those boxes have real widths of 5 (five) to 7 (seven) seconds, while they should actually have a width of 1 (one) second. If the tagname changes are slow, the feature works fine.

A tagname value is not displayed until the value of the tagname changes.

L00015315 The Purge/Archive utility's partial purge function fails; however, the utility can purge the whole database in 4 (four) minutes.

Problem:
The Purge/Archive utility's partial purge function fails, but the utility can purge the whole database in 4 (four) minutes.
After the purge, instead of being shrunk, the size of the database expands to three times over its original size.

Problem:
On the visibility animation link, the ON button is located on the left and the OFF button on the right. On the discrete-value display animation link, the ON button is also located on the left and the OFF button on the right. However, the color-fill animation link has the locations of the buttons reversed; the locations need to be changed for consistency.

L00015540 The condition script's "while loop" does not work correctly.

Problem:
The Timer accumulation is either faster or slower than the actual time. The condition script's while loop does not execute with a frequency based on the timer interval.

L00015569 WindowViewer crashes on open, after the application has had some minor window changes; a tag is also deleted.

Problem:
There are several reports pertaining to the corrupted applications crashing when WindowViewer is started.
The following steps describe the activities that occur before the WindowViewer crashes:

One of the windows is opened and some text that is linked to some tag is deleted.
The window is saved and closed; the use count is updated; any one of the tags is deleted.
A change is made on any window, and then the window is saved.

When WindowViewer is started, it crashes.

L00015617 The 16-Pen Trend crashes in tdatasrc.exe.

Problem:
The 16-Pen Trend crashes in tdatasrc.exe, and a Dr. Watson message is displayed.

Problem:
If the value of a local I/O tag is changed through a user input, the timestamp that is shown to outside sources (WWClient, InSQL, and so on) is not updated properly. If the value changes due to a change at the I/O source, it is updated properly.

What happens is that when the local tag is changed through a local input for the first time, it does not result in the timestamp change. The next time the tag is changed, it takes the timestamp of the previous change. If InSQL is looking at this data, it will now view it as out-of-date (depending on the amount of time lapse between the changes) and will not store it.

The same occurrence happens if the tag is poked by an outside source, such as WWClient.

L00015819 The Purge/Archive utility fails to shrink the database after the purge operation is completed.

Problem:
After the purge operation is completed, the database is not shrunk by the Purge/Archive utility. It should shrink when the purge operation is successful.

L00015936 If an ActiveX Control is active, a frame is shown around this control.

Problem:
If an ActiveX Control is active, a frame is shown around this control. There should not be a halo or frame around the ActiveX Control when it is active.

To disable frames from the ActiveX Control objects, the following line needs to be added to the InTouch.ini file: DisableTouchSelectFrameOCX = 1

L00015939 When using update use counts, the WindowMaker crashes and a Dr. Watson message is displayed.

Problem:
When using update use counts, the WindowMaker crashes and a Dr. Watson message is displayed. Creating a new application using the tag database from the original application and importing these windows will still result in the WindowMaker crashing.

L00015942 The Polygon is changing when a user is switching between the WindowMaker and WindowViewer.

Problem:
When switching between the WindowMaker and WindowViewer, the Polygon is changing.
The application was upgraded from version 5.6 1024x768 (where it ran just fine) to version 7.1 1600x1200.

L00015983 The 16-Pen Trend shows an extra, long vertical line, where there should just be a single point; and, the pen thickness increases at the left of the screen.

Problem:
The pen appears to display erroneous data on the left (old-data) side. An extra, long vertical line is shown where there should just be a single point. This problem occurs when the data moves across the screen.

L00015992 After implementing the hot fix from CR#L00014652, alarms are now being generated when tag.value = tag.HiLimit, or tag.value = tag.MaxEU.

Problem:
After a hot fix for the rounding-off differences (a deviation from the IEEE standards) between the alarm limit and EU dot fields is implemented, the application is now raising alarms for the tag when the value is assigned to match the MaxEU or the HiLimit.

L00016141 WWLogger consumes 100% of the CPU time. This is always initiated by an incomplete line, in the WWLogger, that has garbled characters.

Problem:
WWLogger consumes 100% of the CPU time; an incomplete line, that has garbled characters, in the WWLogger initiates it.

L00016238 Using the TRUNC function to truncate real numbers gives an incorrect result.

Problem:
If 2.01 is assigned to a tagname and the tag is multiplied by 100, the value is then assigned to another tagname, and finally the TRUNC function is used to truncate the second tagname, the result produced by the truncation is incorrect.

Tag1 = 2.01
Tag2 = Tag1 * 100 = 201.00000
Tag3 = TRUNC(Tag2)
The result should be 210, but it is 200.

L00016389 Clicking on the Cancel button will undo the animation link.

Problem:
The visibility link of the wizard becomes unchecked after the Cancel button is clicked on.

L00016427 The new return string feature of QuickFunction in Patch 5a causes memory leak.

Problem:
In Patch 5a, a new feature gives QuickFunction the ability to return a string instead of only integers. This new feature causes memory leak in View.exe.

L00016440 Error messages are logged when a 16-Pen Trend scooter is pasted onto a window, and when a window containing a 16-Pen Trend scooter is opened.

Problem:
Error messages are logged when a 16-Pen Trend scooter is pasted onto a window, and when a window containing a 16-Pen Trend scooter is opened. No error messages should be logged.

L00016548 There are corrupted fonts in the Recipe dialog boxes when the Japanese local settings are used.

Problem:
The fonts in the Recipe dialog boxes change to an unreadable size when the Japanese local settings are used.

L00016751 ptSetPenEx causes the configured pen color to change, and the width to go to the default value of one pixel.

Problem:
The color of a pen was set to a color other than the default; when the ptSetPenEx function on that pen is called, it changes both the pen color and the width to the default values.