InSQL 7.0 SP2 Patch 02 Readme

(c) Copyright Wonderware Corporation, 2000


This document provides information about fixes and enhancements supplied with InSQL 7.0 SP2 Patch 02.

 


Resolved Issues

I0002737 Bad time stamp is returned when querying past midnight.

I0003277 Trend: The legend for Y-scale does not show decimal places at low resolution.

I0006070 Reimport of existing tagname.x with new node name in Access Name doesn't associate tags.

I0006649 Vector Master: An error message should be shown when trying to modify tags or delete trace in Run Mode.

I0006762 Improper datetime format causes PDSSRV to stop without warnings.

I0007099 Summary Generator: Does not recover two periods back.

I0007117 Vector Master: Menu items in the context menu on the Traces page should be greyed out when in Run mode.

I0007127 Import and reimport always resets the WideColumnName field regardless of CurrentEditor setting.

I0007171 Vector Master: An error message should be shown when trying to modify tags or delete trace in Backdrop Edit Mode.

I0007577 InSQL Control: "Error Opening SC Manager".

I0007669 INSERT INTO problem with nested "SELECT MisspelledColumnName FROM AnalogWideHistory".

I0007962 Stored procedure 'xp_AnalogWideHistory' generates Access Violation: "SQL Server is terminating process 14."

I0007970 Config Editor: The drag and drop stops working after using copy and paste to add a tag to a group.

I0008052 Trend: Print does not display values over 999.99.

I0008477 Bad data returned from query using analog cyclic retrieval and datetime.

I0008506 Vector Master: An access violation is received when deleting an unselected trace in Run mode.

I0008645 Timestamp returned for midnight and noon misrepresented in 12 hour time format.

I0008812 Cyclic retrieval returning wrong values for specific queries at history block changeover time.

I0008887 Trend: Each Print Preview leaves behind a large QRP*.TMP file without deleting it.

I0009334 Inconsistent delta retrieval.

I0009537 Trend: Cursor values for X-Axis and Y-Axis not displayed with proper decimal precision.

I0010458 Query returns wrong data when particular tagnames are included.

Back to Top


 

Detailed description

 

I0002737 Bad time stamp is returned when querying past midnight.

Problem: When the start time of a query lies before midnight, and the end time lies after midnight, then certain queries would return an invalid time stamp for one row of returned data. This was caused by an inadequate check for the time stamp passing midnight.

Resolution: Check for valid time stamps implemented.

Back to Top

I0003277 Trend: The legend for Y-scale does not show decimal places at low resolution.

Problem: For tags Y-scaled from 0 to 1 the legend on the left side is not displaying any decimal places for the ticks. Should look like "0, 0.25, 0.5, 0.75, 1" but really looks like "0, 0, 1, 1, 1".

Resolution: Legend for Y-scale now shows decimal places at low resolution.

Back to Top

I0006070 Reimport of existing tagname.x with new node name in Access Name doesn't associate tags.

Problem: If the access name was changed in InTouch for an existing IO Tag on an imported node, then a reimport of the node did not update the IOServerKey field of the Tag table. The cause of the problem was an import flag set to false.

Resolution: Fixed by setting the import flag to true.

Back to Top

I0006649 Vector Master: An error message should be shown when trying to modify tags or delete trace in Run Mode.

Problem: If a user is trying to modify tags or delete trace while in Run Mode in Vector Master no error message is shown. User should be warned that modification or deletion is not allowed.

Resolution: Error message added.

Back to Top

I0006762 Improper datetime format causes PDSSRV to stop without warnings.

Problem: Queries with different errors in the used datetime format would crash PDSSRV without warning. The cause was insufficient format checking before passing the datetime on to ODS for conversion.

Resolution: Introduced a new function for checking if the datetime complies with the supported formats. If not an error message to that effect is returned.

Back to Top

I0007099 Summary Generator: Does not recover two periods back.

Problem: Even though the Administrator's Guide states, that the Summary Generator would recover summaries for two periods after a down time, it really only recovered one per design.

Resolution: Added the feature as documented.

Back to Top

I0007117 Vector Master: Menu items in the context menu on the Traces page should be greyed out when in Run mode.

Problem: If you right click in the list box on the Traces page of the Property panel, a context menu appears with three commands. These should all be greyed out when a trace is in Run mode.

Resolution: Fixed together with CR I0008506.

Back to Top

I0007127 Import and reimport always resets the WideColumnName field regardless of CurrentEditor setting.

Problem: After an import or a reimport the WideColumnName field of the Tag table in the Runtime database was modified regardless of the current editor setting of the tag. If a change had been made to this field, it would be lost after a reimport.

Resolution: With this fix the stored procedure ww_Cleanup_AfterImport checks if the tag is using InSQL as the current editor. If so, the field value is not changed.

Back to Top

I0007171 Vector Master: An error message should be shown when trying to modify tags or delete trace in Backdrop Edit Mode.

Problem: If a user is trying to modify tags or delete trace while in Backdrop Edit Mode in Vector Master no error message is shown. User should be warned that modification or deletion is not allowed.

Resolution: Error message added.

Back to Top

I0007577 InSQL Control: "Error Opening SC Manager".

Problem: If you set InSQL Control to start up automatically, and then logged off and back on as just a normal non-Administrative user, you would see "Error Opening SC Manager" over and over in the Control window.

Resolution: A check is now made to see, if the user has administrator rights. If not, the controls for starting and stopping the services are disabled.

Back to Top

I0007669 INSERT INTO problem with nested "SELECT MisspelledColumnName FROM AnalogWideHistory".

Problem: If a nested query within an INSERT INTO failed, the system would hang, because the INSERT INTO code would continue to wait for the failed statement to finish.

Resolution: Proper error handling routine has been added to solve the problem.

Back to Top

I0007962 Stored procedure 'xp_AnalogWideHistory' generates Access Violation: "SQL Server is terminating process 14."

Problem: When running certain queries involving extended stored procedures, an Access Violation would occur. The cause of the problem was, that several extended stored procedures were passed a NULL parameter.

Resolution: Proper error handling of NULL parameters have been implemented.

Back to Top

I0007970 Config Editor: The drag and drop stops working after using copy and paste to add a tag to a group.

Problem: If you used copy and paste to add a tag to a user defined group, the drag and drop method would stop working. The problem was caused by improper handling of mouse button messages.

Resolution: Handling of mouse button messages fixed.

Back to Top

I0008052 Trend: Print does not display values over 999.99.

Problem: The print from Trend would show '******' in any numeric field, where the value exceeded 999.99. The problem was caused by bad data conversions.

Resolution: The data conversions have been fixed.

Back to Top

I0008477 Bad data returned from query using analog cyclic retrieval and datetime.

Problem: Bad values were returned from a query requesting only one single value in analog cyclic retrieval mode. The problem was caused by some inadequate DateTime comparisons.

Resolution: Values are now returned properly.

Back to Top

I0008506 Vector Master: An access violation is received when deleting an unselected trace in Run mode.

Problem: When a Trace other than the running Trace was deleted an Access Violation occurred.

Resolution: With this fix the menu items "Insert", "Modify" and "Delete" in the context menu and the menu item "Insert" in the pull down menu have been disabled while in Run mode.

Back to Top

I0008645 Timestamp returned for midnight and noon misrepresented in 12 hour time format.

Problem: A query executed with 12 hour time reference would return wrong timestamps. Noon was returned as 12:00:00AM and midnight was returned as 00:00:00AM.

Resolution: Changed to return proper time.

Back to Top

I0008812 Cyclic retrieval returning wrong values for specific queries at history block changeover time.

Problem: When running a cyclic retrieval incorrect values at history block changeover time were returned for queries specifying a start time where the seconds were either 33, 39, 45, 51, or 57. Was caused by inadequate DateTime comparisons.

Resolution: DateTime comparisons have been changed, and the queries now return the proper values.

Back to Top

I0008887 Trend: Each Print Preview leaves behind a large QRP*.TMP file without deleting it.

Problem: Whenever you did a Print Preview, it would leave a rather large file behind in the TEMP directory.

Resolution: The Preview function has been changed to properly clean up after itself.

Back to Top

I0009334 Inconsistent delta retrieval.

Problem: If you ran the stored procedures WW_SetAnalogCyclic Off and WW_SetRowcount, and then a simple SELECT statement using datetime, you would have to run the query a couple of times, before any data were returned. The problem was caused by a NULL value assignment, which lead to an unhandled exception error.

Resolution: Checking for proper initialization and proper handling of the thrown exception have been added to fix the problem.

Back to Top

I0009537 Trend: Cursor values for X-Axis and Y-Axis not displayed with proper decimal precision.

Problem: Graph cursor displays were not consistent with the format of the Y-Axis scale. For example, the X-axis cursors always have a two fixed decimal places, but the Y-axis cursor had a problem rounding to the nearest integer. The problem was caused by conversions from float to string.

Resolution: The data conversions and the format of the cursors have been made consistent throughout the module.

Back to Top

I0010458 Query returns wrong data when particular tagnames are included.

Problem: Query returned wrong data when particular tagnames were included. The problem was caused by some missing data block loads.

Resolution: Data block loading has been fixed, and the correct rows are returned.

Back to Top