InTouch® 7.

1 Patch 08 ReadMe
© 2002 Invensys System, Inc. All Rights Reserved.

This document provides information regarding bugs fixed in this patch

and other known issues.

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.

I0007666 DB Load fails at embedded spaces in a tagname's DDE

Access Name.

I0009887 The 16-pen Trend does not refresh trend and time stamps
properly.

I0014110 Button wizards - WindowMaker resizes button wizards when

a window is saved, closed, and then opened.

I0014578 Installing and then uninstalling the wizard generator will

crash WindowMaker.

I0015841 InTouch is unable to distinguish the keypad

characters/symbols - from . (minus and period).

I0016910 Enhancement Request - The New Script function is

requested to return status information on a window's state
(open/closed).

I0017385 There is a problem importing a window.

I0018619 WindowMaker - WM.exe crashes when WindowMaker is shut

down while the Selection Box window is displayed.

I0019478 The error message in WWlogger that is related to

GetPropertyM() is to be removed.

I0019610 ptSetTimeAxisToCurrent does not work.

I0019638 The Alarm Logger printout format needs alignment
adjustments.

I0019641 The X or Y location of a window changes when the Width or

Height of the window is manually reduced.

I0019655 The item "ERROR" defined in the HistData program

concatenates the previous error.

I0019683 The Alarm button does not function when the SPC dataset is
made using the Duplicate button.

I0019817 ActivateApp - The SendKeys script combination is not

executing properly.

I0019838 There is Historical Time Difference when InSQL is used as a

historical provider.

I0019933 $DateString does not bring back the date as configured in

the Control Panel.

I0019946 Quick function call, which has a name more than eight (8)
characters long, causes AE (Assertion Error) and WindowViewer to
freeze.

I0019959 ShowTopLeftAt() does not function as it did prior to InTouch

7.0 SP2 Patch 03. The Replace-type windows close in WindowViewer,
even though they are not touching in WindowMaker.

I0020036 Trend Object scans every time it is initialized, and Scooter

change takes a long time to update.

I0020124 The Cross Reference utility is not returning correct

information for the object size and position.

I0020171 Stringfromtime() and StringFromTimeLocal() do not follow

the ControlPanel/RegionalSettings format.

I0020178 A return to normal entry is not given the Return color, if the
tag was Acknowledged prior to its return to normal.

I0020181 AlarmParetoPlus returns a "Runtime error 6 Overflow."

I0020192 SQL Access Manager - If an application has not created an

SQL.def file when a connection is attempted, a -1005 internal error is
returned to the result code.
I0020197 AlarmTree ActiveX Object - the selected-item highlight
jumps around.

I0020201 The "dot field" import creates a new tag, when an attempt is
made to import and the dot-field tag is converted to a remote tag.

I0020267 The .AlarmEnabled dot-field retentive value is lost if "Update

Use Count" is used on the application.

I0020268 Error HTSPT/HTSetPenName: "FT701EU Invalid Trend Tag."

I0020269 The remote-tag count is incorrect.

I0020352 The List Box control has graphical remnants on the top and
left borders.

I0020559 When a window is moved by using the mouse, its x-and-y

position does not change.

I0020639 SPCPro crashes while an attempt is made to duplicate a

Dataset.

I0020722 Alarm Logger Configuration setting: Cannot set HH:MM:SS

and HH:MM for time format in the Message tab.

I0020775 There is invalid data in the Value field when a discrete tag is
used.

I0020781 SPC Dataset is saved without the product name when the
<Enter> key is used.

I0020787 Line Printer for alarm printing limits the flexibility of the
printer's usage.

I0020818 The Tagname button does not work after some Retentive
Memory tags are deleted, and then an attempt is made to modify a
BindList.

L00005040 A Dr. Watson error message is generated when

WindowViewer is shut down.

L00005760 SQLSetParamChar is not working if more than one Char

parameter is set.

L00006386 InTouch is not rounding up Real values properly - values in

this test have only four (4) digits.

L00007485 Historical logging stops at midnight.

L00007486 Historical Trend Object shows a data time-stamp at +14
hours ahead of the actual logged time.

Back to Top

Detailed Description

I0007666 DB Load fails at embedded spaces in a tagname's DDE

Access Name.

Problem:
DB Load fails at embedded spaces in a tagname's DDE Access. No
space was removed when the dbload was performed.
However, please be aware that the access name with invalid
characters, such as a space, could not be used with the remote tags;
a warning was given when an invalid access name was created.

Back to Top

I0009887 The 16-pen Trend does not refresh trend and time stamps
properly.

Problem:
After the 16-pen Trend has been running for a while, it stops
repainting the trend and time stamps properly. The time stamps
show only the time in seconds, and the start time is not the same for
all tags in the trend.

Back to Top

I0014110 Button wizards - WindowMaker resizes button wizards when

a window  is saved, closed, and then opened.

Problem:
In WindowMaker, if one of the wizards is added to a window from the
Wizard Selection/Buttons menu, then the window is saved, closed,
and reopened, the object is a different size.

Back to Top

I0014578 Installing and then uninstalling the wizard generator will

crash WindowMaker.
Problem:
When WindowMaker called the FreeLibrary() to remove WWB, the
parent window became hidden.

Back to Top

I0015841 InTouch is unable to distinguish the keypad

characters/symbols - from . (minus and period).

Problem:
InTouch is unable to distinguish the keypad characters/symbols -
from . (minus and period).
The two keys are located on either side of the zero, and are nearly
impossible to distinguish unless the system font is set to 200% its
normal size on Windows 2000. The fonts on NT are large, and both
characters/symbols are still not easily identifiable. Setting the system
font to 200% causes major problems for the rest of the system, and
is not a viable workaround.

Back to Top

I0016910 Enhancement Request - The New Script function is

requested to return status information on a window's state
(open/closed).

Problem:
A Script function, that will either give information whether a window
is open or not, or return a list containing the currently open
window(s), is requested.

Returns the Window Status of the specified Window.

Syntax: IntegerResult = WindowState("Window Name");

Parameter Description
======= =======

WindowName: The Name of the Window whose status is to be

determined. Actual string or message tagname.

Remarks: Return type is 0, 1, or 2, and it is assigned to the

IntegerTag.

Example(s):

    WindowState("Win1") will return 1, where "Win1" is the name of

the defined window and is currently open.
    WindowState("Win2") will return 0, where "Win2" is the name of
the defined window and is currently not open.

    WindowState("XXXX") will return 2, where "XXXX" is the name of

the window, which is not defined.

Returns the List of Open Windows in a DialogBox.

Syntax: OpenWindowsList();

Remarks: During runtime, a dialog box with the title "Open Windows
List" is displayed, and all the InTouch windows which are open at that
given point are shown in a dialog box.

Back to Top

I0017385 There is a problem importing a window.

Problem:
An error is displayed when one of the windows is imported.

Back to Top

I0018619 WindowMaker - WM.exe crashes when WindowMaker is shut

down while the Selection Box window is displayed.

Problem:
When the "BindList" under the SQL Access Manager tree node is
clicked on, a Selection Box, which is a pop-up window, is thrown up.
From then on until the dialog box is closed, all the messages are
dispatched to the Selection Box Window Procedure.
When the Selection Box window is closed by selecting the Cancel
button or by clicking on a point other than the Selection Box,
POSTMESSAGE is posted to the Selection Box Window Procedure; this
will destroy the window.

Back to Top

I0019478 The error message in WWlogger that is related to

GetPropertyM() is to be removed.

Problem:
When No Alarm is selected, and the following script:
"ErrorNumber=GetPropertyM("ALMOBJ_1.AlarmProv",tag1);" is
executed, it will result in "ErrorNumber=-1" and "Tag1=blank," and
an error in the WWlogger.
The problem is, these errors fill the WWlogger; it is requested that
the logger messages be eliminated since "ErrorNumber=-1" is all that
the Error needs.

Back to Top

I0019610 ptSetTimeAxisToCurrent does not work.

Problem:
ptSetTimeAxisToCurrent does not work. There are two problems: the
Start Time is set to current time, and documented parameters do not
exist.

This function should at least use the current span and set the End
Time of the trend to the current time. It does not; it sets the Start
Time to the current time, showing the span, but in the future, where
there is no logged data.
It should also have two parameters. The first is for the trend object
name, and the second being a parameter for its span, either "Current
Span" or a specific Start Time; and then it should use the current
time for the End Time.

Back to Top

I0019638 The Alarm Logger printout format needs alignment

adjustments.

Problem:
In Alarm Logger, Output/Configure...-> Message format, each field
can be given a width of the column in the printout. However, "value"
and "limit" fields are not bound by the width settings, no matter what
the width values are. Even with "Remove trailing spaces" unchecked,
the "value" and "limit" fields are still misaligned on the printout,
which causes the rest of the columns after them to also misalign.

Back to Top

I0019641 The X or Y location of a window changes when the Width or

Height of the window is manually reduced.

Problem:
The X or Y location of a window changes when the Width or Height of
the window is manually reduced.

Back to Top

I0019655 The item "ERROR" defined in the HistData program

concatenates the previous error.
Problem:
The item "ERROR" defined in the HistData program concatenates the
previous error.
Item "ERROR" in HistData Program contains a description of the last
error. It will be "None" when STATUS is 1 (one), and will contain an
error-message string when STATUS is 0 (zero). But when an error
appears more than once, then it concatenates with the previous error
message; only when there are no errors in the program, does it
display the None.

Back to Top

I0019683 The Alarm button does not function when the SPC dataset is
made using the Duplicate button.

Problem:
When the Alarm button is clicked, SPCPro invokes the SPC Alarm
Selection dialog box only if the alarm set object has already existed,
even if the database has no alarms configured for the current dataset
yet. However, if a dataset is duplicated, no alarm set objects are
created.

Back to Top

I0019817 ActivateApp - The SendKeys script combination is not

executing properly.

Problem:
The SendKeys message is not being executed.

Back to Top

I0019838 There is Historical Time Difference when InSQL is used as a

historical provider.

Problem:
When Using InSQL as a Historical provider, there is a problem with
timezones that are GMT +.
InTouch shows the Historical data as being in the past (that is, a
point that was recorded at 20:11 would show in the Historical display
as being recorded at 18:11, if the Time Zone is GMT + 2), while the
data that is logged by InTouch is correct.

Back to Top

I0019933 $DateString does not bring back the date as configured in

the Control Panel.
Problem:
$DateString is displayed as 25-02-02, when the settings are changed
via the Control Panel-> Regional Settings to dd/mm/yy. It should be
displayed as 25-Feb-02.

Back to Top

I0019946 Quick function call, which has a name more than eight (8)
characters long, causes AE (Assertion Error) and WindowViewer to
freeze.

Problem:
When calling a Quick function that has a name more than eight (8)
characters long, the Assertion Error and WindowViewer freeze.

Back to Top

I0019959 ShowTopLeftAt() does not function as it did prior to InTouch

7.0 SP2 Patch 03. The Replace-type windows close in WindowViewer,
even though they are not touching in WindowMaker.

Problem:
The new behavior was implemented by CR# I0000894 (InTouch 7.0
SP2 Patch 03). There is a functionality change because the new
InTouch version does not have backward compatibility.
The NewShowAt entry in the InTouch.ini file is used to control the
behavior.
In order to allow applications, using the change implemented for CR#
I0000894, to behave in the same manner without any additional
changes, the default for NewShowAt is set to 1.
For those who would like to keep the first window open, it is
necessary to add NewShowAt=0 to this .ini file.

Back to Top

I0020036 Trend Object scans every time it is initialized, and Scooter

change takes a long time to update.

Problem:
Trend Object scans every time it is initialized, and Scooter change
takes a long time to update.

Back to Top

I0020124 The Cross Reference utility is not returning correct

information for the object size and position.
Problem:
The problem reported in this CR occurs if the Cross Reference utility
is run after the window is closed, or after the window is closed then
reopened. If the window is closed and Cross Reference utility is run,
InTouch will try to load the window to get the definition of different
objects on the window. When loading a symbol object, initially
different objects in the symbol, with which it is composed of, are
loaded and then the union of all the rectangles is done to get the total
size and coordinates of the symbol object.

In this CR, the symbol object is composed of two horizontal lines.

Each horizontal line is treated as a separate object at the time of
loading, so it will be a rectangle of height zero. When two rectangles
of height zero are passed to UnionRect() function, the action results
in a rectangle of size 0 (left = 0, top =0, bottom = 0, right = 0). This
is the reason the coordinates are seen as zeros when the Cross
Reference utility is run.

Back to Top

I0020171 Stringfromtime() and StringFromTimeLocal() do not follow

the ControlPanel/RegionalSettings format.

Problem:
Stringfromtime() and StringFromTimeLocal() do not follow the
ControlPanel/RegionalSettings format.

Back to Top

I0020178 A return to normal entry is not given the Return color, if the
tag was Acknowledged prior to its return to normal.

Problem:
When the Alarm Object is configured, there is a color for Ack, Alarm,
and Return. Under any circumstances, the color should represent the
current situation. For instance, whether the tag has been
ackowledged or not, and has now returned to normal, it should be the
color set for "Alarm Return." When the tag is Acknowledged, whether
it has returned to normal or not, it should show the color for "Ack
Alarm."

Back to Top

I0020181 AlarmParetoPlus returns a "Runtime error 6 Overflow."

Problem:
AlarmParetoPlus queries data from the AlarmDurations and
AlarmSummary tables; if there are no records in these two (2) tables,
it will return "No records found" message. If the values of the
EventDuration fields in the AlarmDurations table are equal to zeros, it
will return the error message, "Runtime error 6 Overflow."

Back to Top

I0020192 SQL Access Manager - If an application has not created an

SQL.def file when a connection is attempted, a -1005 internal error is
returned to the result code.

Problem:
A new SQL error message, "-1014 The Sql.def file does not exist,"
needs to be added to the already-existing list.

Back to Top

I0020197 AlarmTree ActiveX Object - the selected-item highlight

jumps around.

Problem:
If one item in the tree is clicked on, the correct item is selected and
passed through, but the cursor highlight moves to a totaly different
object. This causes confusion for the user; and it makes the object
appear to be broken.

Back to Top

I0020201 The "dot field" import creates a new tag, when an attempt is
made to import and the dot-field tag is converted to a remote tag.

Problem:
The "dot field" import creates a new remote tag that combines the
main tag with the dot-field extensions. The new remote tag
eliminates the "dot field" functionality.

Back to Top

I0020267 The .AlarmEnabled dot-field retentive value is lost if "Update

Use Count" is used on the application.

Problem:
The .AlarmEnabled dot-field retentive value is lost if "Update Use
Count" is used on the application.
If "Alarm Enable Retentive" is set and the .AlarmEnabled field of a tag
is disabled or reset, WindowViewer is closed, WindowMaker is run,
and the "Update Use Count" is utilized, the .AlarmEnabled dot field
will go back to "Set" or "Enabled," when WindowViewer is restarted.
 Back to Top

I0020268 Error HTSPT/HTSetPenName: "FT701EU Invalid Trend Tag."

Problem:
Error HTSPT/HTSetPenName: "FT701EU Invalid Trend Tag" appears
when dot fields are used in more than one parameter for the
htsetpenname().

Back to Top

I0020269 The remote-tag count is incorrect.

Problem:
When the remote references point to a dot field for remote alarm
groups, and if links to remote references are created pointing to a dot
field in remote alarm groups, such as
"AccessName:AlarmGroup1.Alarm" and
"AccessName:AlarmGroup2.Alarm," the error message can be seen
being displayed twice for the second link, as if the feature was
attempting to activate two tags instead of just one.

Back to Top

I0020352 The List Box control has graphical remnants on the top and
left borders.

Problem:
The List Box control has graphical remnants on the top and left
borders.
If a List Box is placed on a window, then you go to runtime and move
the window around, the top and left edges on the List Box do not
redraw correctly. There are graphic artifacts left on the edges.

Back to Top

I0020559 When a window is moved by using the mouse, its x-and-y

position does not change.

Problem:
When a window is moved by using the mouse, its X-Y-location
information does not change.

Back to Top

I0020639 SPCPro crashes while an attempt is made to duplicate a

Dataset.
Problem:
When an attempt is made to duplicate a Dataset, after the last
Dataset was created and saved, without creating a product and by
using the <ENTER> key, SPCPro crashes.

Back to Top

I0020722 Alarm Logger Configuration setting: Cannot set HH:MM:SS

and HH:MM for time format in the Message tab.

Problem:
Alarm Logger Configuration setting: Cannot set HH:MM:SS and
HH:MM for time format in the Message tab.

Back to Top

I0020775 There is invalid data in the Value field when a discrete tag is
used.

Problem:
When one InTouch application with alarms is created using a discrete
tag, and any value message other than ON & OFF is used, the values
of the "VALUE" field in the Alarm Summary are not correct.

Back to Top

I0020781 SPC Dataset is saved without the product name when the
<Enter> key is used.

Problem:
The SPC Dataset is saved without the product name when the
<Enter> key is used. It is requested that the application give a
warning message, "You must create a Product for this new Dataset
first." before the dataset is saved; and, the SPC Dataset
Configuration must be prevented from closing if no products have
been created for the dataset.

Back to Top

I0020787 Line Printer for alarm printing limits the flexibility of the
printer's usage.

Problem:
The earlier version of Windows operating system, for example: Win
NT, was not supported with plug-and-play devices. The printer used
to be configured as the default printer, to print InTouch alarms,
without the printer-driver software installed. However, now Windows
2000 and Windows XP provide the plug-and-play service. It detects
the printer and the OS installs the printer-driver software, thus
making it incompatible for InTouch alarm printing. According to
Wonderware Tech Note 149, alarms can be printed out through the
network; this method still works, but only with physical-parallel-ports
printer, not with com-port, USB-port, or virtual-port printers.

The temporary workaround is to disable the plug-and-play service,

dedicate the printer only for printing InTouch alarms, and not have it
supported for printing out other applications' materials like MS Word
documents, Excel reports, and others. This really is an issue, because
most computers come with more than one COM port or USB port, and
only one parallel port. If the Alarm Printing utility is supported with a
COM port or a USB port, one of the ports can be mapped for network
printing and the parallel port for regular reports or alarms. To achieve
the same capability, two dedicated parallel ports are now needed.

In summary, the Alarm Printing utility should be able to print to any

installed printer (network, USB, serial, or parallel) and use the driver
to that printer.

Back to Top

I0020818 The Tagname button does not work after some Retentive
Memory tags are deleted, and then an attempt is made to modify a
BindList.

Problem:
When some Retentive Memory tags are deleted and an attempt is
then made to modify a BindList, the Tagname button does not work.

Back to Top

L00005040 A Dr. Watson error message is generated when

WindowViewer is shut down.

Problem:
This problem occurs only on a WinNT 4.0 SP6a computer with
WindowViewer running as a service.
A Dr. Watson error message is generated when WindowViewer is shut
down.

Back to Top

L00005760 SQLSetParamChar is not working if more than one Char

parameter is set.

Problem:
When SQLSetParamChar is used to set the parameters of a stored
procedure, to be executed using SQLSetStatement,
SQLPrepareStatement, and SQLExecute, and the stored procedure
that is to be executed is an insert statement, then the data sent to
the procedure becomes bad the second time an SQLSetParamChar is
used.

Back to Top

L00006386 InTouch is not rounding up Real values properly - values in

this test have only four (4) digits.

Problem:
When creating a Memory Real tag with an analog input link that also displays "##.##,"
a value input of 1.595 that is typed in will be shown as 1.59. Most numbers with a
5 (five) as the last digit after the decimal (.) are not rounded up. Only
one number is rounded up, 3.595 rounds up to 3.60.

Back to Top

L00007485 Historical logging stops at midnight.

Problem:
When the computer clock goes to midnight, no new historical log files are created; no
new data is seen in the Trend Object if it is updated, and no errors show in the
WWlogger files either.

Back to Top

L00007486 Historical Trend Object shows a data time-stamp at +14

hours ahead of the actual logged time.

Problem:
Data logged at 8:00 A.M. shows a time stamp of 10:00 P.M. in the Historical Trend
Object.

Back to Top