|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
9245
|
Alarm Management
|
In certain cases problems would occur recording the TimeStamp of an alarm.
|
|
9226
|
Alarm Management
|
In certain cases Movicon would remain pending in the Alarm Manager arrest phase when stopping a project. This would happen when a large number of defined variables connected to an OPC that were also connected to project alarms changed value quickly.
|
|
9161
|
Alarm Management
|
Changes to a project's Runtime User files would regenerate the Runtime Users List in the Parent project only, while any existing child projects, which shared the same file, would not load the updated list and continued using the initial users list present in the file at project startup.
|
|
9138
|
Basic Scripts
|
The "Sub Loading()" event of a Basic Script would not get executed if inserted within a Script shared through the "'#Uses" function.
|
|
9326
|
Basic Scripts
|
In certain conditions when executing a script code in an alarm's threshold an “(0) Active X error code = 0x8000ffff" error message would get generated.
|
|
9013
|
Basic Scripts
|
The 2 bit of a basic script's state variable would not get managed if script went into error. The 2 bit now changes to 1 if an error occurs and stays at 1 until the error window opened by the script is confirmed. The bit is zeroed upon closing window.
|
|
9276
|
Basic Scripts
|
The "KeyDown" and "KeyPress" Script events used in a screen and in an objected would not always be notified correctly.
|
|
9363
|
Basic Scripts
|
When executing a script an "(0) ActiveX error code = 0x8000ffff" error would get generated. This problem was caused to the fact that the "InUse Objects Manager" was active.
|
|
9064
|
Comm.Drivers
|
The DataLogger, in certain situations when linked to the Communication Driver, would record the same record twice at project startup.
|
|
8367
|
Comm.Drivers
|
Only up to 116 Communication Drivers could be loaded in Windows Server 2003 and not more.
|
|
8965
|
Data Loggers Management
|
A Data Logger's "Print Tag " would not execute the Print command of the report associated to the DataLogger.
|
|
9033
|
Data Loggers Management
|
On several occasions a DataLogger's status variable would remain at the value "1" instead of returning to the value "0" while restoring the ODBC connection after an error had occurred.
|
|
9000
|
Data Loggers Management
|
A DataLogger's status variable would not get saved in the DataLLoggers file and therefore would not result when the project was reloaded afterwards. In addition it became impossible to set status variables for Recipe resources when project had been set with a Basic License.
|
|
8919
|
Data Loggers Management
|
When an array variable was used in a DataLogger as a record variable, two identical records would get inserted in the database.
|
|
8901
|
Design
|
When a Parent project inserted a Child project screen as its startup screen by specifying only the Child project's name comprising the dos bar and not that of the screen, Movicon would raise an error when validating modification.
|
|
8987
|
Design
|
When activating the command to create a variable group after having selected a member from a structure prototype, Movicon would raise an error.
|
|
9380
|
Design
|
Some problems would occur when referencing a Parent project variable from a Child project when this variable has been defined both at Parent and Child project level. This occurred mainly when inserting such variables in basic script expressions belonging to objects.
|
|
9188
|
Design
|
Selecting an object within a screen would not always populate the Property Window which remained blank. This problem would verify in concurrence of the following conditions:
-
Object used a structure variable in a basic expression enclosed between rounded brackets (i.e. "(MyStruct.VAR00001)")
-
The structure variable member was referenced within the expression using a full stop
-
The structure variable had its intellisense active
|
|
9409
|
Design
|
It no longer became possible to edit more than 259 characters in a screen's Alias Table or Parameter File.
|
|
8961
|
Design
|
In certain conditions saving a project would result with an empty ".movrealtimedb" file with project remaining in the 'Unsaved' status.
|
|
9413
|
Design
|
The SouceSafe command "Get Last Version" would not reset the compiled files (files with "_c" extension) and the Driver's ".dynsettings" file.
|
|
9357
|
DOM (Document Object Model)
|
The "ReconnectAll" function form the "OPCClientCmdTarget" interface would not work correctly.
|
|
9295
|
DOM (Document Object Model)
|
Setting the "Variable" and "EnableVariable" properties from the "EventCmdTarget" interface would have no effect.
|
|
9385
|
DOM (Document Object Model)
|
"GetZoomAreaDateTime*" functions in a Trend object would return an incorrect date equal to "30/11/1999". This problem would happen when the vertical cursor from the zoom area was in the Trend's start area which did not contain valid dates in the X axis time base.
|
|
9038
|
DOM (Document Object Model)
|
The "Print" property from the "AlarmThresholdCmdTarget" would not work. When this property was modified in Runtime the Alarm would not acknowledge the property's new value.
|
|
9369
|
DOM (Document Object Model)
|
In certain conditions the "GetAlias", "GetAliasListName" and "GetAliasListValue" function from the "SynopticCmdTarget" and "DrawCmdTarget" interfaces would fail.
|
|
8405
|
Events Resource
|
Events associated to a Parent Project's structure variable member would not get executed in a Child Project.
|
|
9214
|
IMDB (In Memory DB)
|
A recipe memorized on IMDB database was presumed deleted when going into runtime with the project, but apparently the file did not get deleted but renamed from ".dat" to ".datbackup".
|
|
8947
|
License
|
When using a "Basic" License, the Trend object would not get managed correctly and would not show data in runtime.
|
|
8964
|
License
|
The "Alarm Dispatcher" option would not show in the Licence Requirements window.
|
|
9347
|
Networking
|
The filter applied to alarm priorities in a Network Client Alarm Window would not work correctly.
|
|
8927
|
ODBC
|
Problems would occur when creating flush files to accommodate ODBC connection errors. This would particularly happen if the DSN had been created as "User DSN" instead of "System DSN".
|
|
9393
|
ODBC
|
The SQL Server 2005 and 2008 ODBC plug-in would not use the driver set in for default in the source code.
|
|
8966
|
OPC Communication
|
A project set for connecting to one or more OPC Servers would generate a rather misleading error message in the log when one or more OPC Servers were unavailable at project startup. This message has now been changed whereby setting the "Reconnection Time" to the '0' value no attempt will be made to reconnect to the Server by Movicon after a first connection error occurrence.
|
|
8897
|
OPC Communication
|
The quality of an OPC item would not get managed correctly if the item in question was non existent.
|
|
9230
|
OPC Communication
|
Problems with updating variable qualities connected with the OPC Server Factory Talk (Rockwell).
|
|
8944
|
Real Time DB
|
When using a array variable connected to a Communication Driver and one or more of its elements went into use for the first time, the Driver would execute a array variable write even though the variable's value had not changed.
|
|
8635
|
Real Time DB
|
Values with floating points saved in a database had a limited 6 figure precision after the point. This precision is now managed according to the "FloatingPointPrecision" registry key.
|
|
9009
|
Real Time DB
|
When a structure variable was expanded within the Watch window to see the values of each individual member, these values would show set to 'unknown' when changing tab and then returning back again.
|
|
9035
|
Recipes Management
|
Some recipe status variable bits would not work properly.
|
|
9078
|
Recipes Management
|
Setting the Movicon language to German and then creating a new Recipe resource, the name of the "Recipe Index" column would insert as "Rezept-Index". This would then create a problem due to the fact that not all databases support the "-" character. This character is now nolonger inserted.
|
|
8955
|
Recipes Management
|
When a Float Array variable was used in a Recipe object, the values loaded from the database would lose their decimal part.
|
|
9115
|
Report Management
|
The Pen Points of a Movicon Embedded Report's Chart/Trend in WinCE would show enlarged.
|
|
8799
|
Report Management
|
Reports could not be viewed from Child projects in a Network Client created with Parent-child architecture. It is now possible to do so providing that the ODBC connection used by the Child project for recovering data is linkedto the Server project's database.
|
|
9100
|
Report Management
|
Generating a Movicon Embedded Report would take up a lot of time when containing more than few pages. Now in Win32/64 bit performances have been very much improved, but only if transparency or visibility animations are not used in the report.
|
|
8946
|
Report Management
|
The union query in the Movicon Embedded Reports which is executed in the Historical Log window would only apply the data filter in the last table.
|
|
9507
|
Report Management
|
The Embedded Report management had not been enabled in the Movicon BA version.
|
|
9390
|
Screen Management
|
The Maximize and Minimize buttons would not display in a window opened in "Frame" mode even though the their relating options had been activated. Now, likewise with Modal windows, the Minimize (reduce) button even though displayed is always disabled.
|
|
9031
|
Screen Management
|
The use of Aliases in object "Default Structure" fields would not function.
|
|
9077
|
Screen Objects
|
When a Trend object was stopped from a Network Client or Web Client, the time reported in the "Break Values Area" was incorrect.
|
|
1061
|
Screen Objects
|
The OnColumnClick event would not function and if there was associated script code it was not performed.
|
|
8893
|
Screen Objects
|
When changing pages among screens containing Embedded Screens, the events of the Embedded Screen objects would not be notified. As a consequence these objects would not respond to any click operations. This condition would come into being if the Screens had been enabled with the "Keep in Memory" option.
|
|
8889
|
Screen Objects
|
Moving an object with animated movement in progress within a screen inserted as an Embedded Screen had negative results if the "Keep in Memory" option had been enabled in the main screen.
|
|
9046
|
Screen Objects
|
When the temporary log was displayed in an active Alarm Window, the status change of the alarm's variable a Message Box would appear showing an "Invalid Argument" error message.
|
|
8973
|
Screen Objects
|
When an Embedded Screen or TAB Group was used in a Parent project for displaying a Child screen, the command of these screen would execute within the context of the Parent project and therefore would not function correctly above all if Parent project had several Child projects using resources with the same name (i.e. screen names). These commands are now executed by searching the resources first in the Child project.
Incompatibility:
This fix may cause problems in projects from previous versions in cases where, for example, commands executed from Child projects have been "adapted" to work around the original problem of this case.
|
|
9094
|
Screen Objects
|
A Display object's "OnTextChanged" event would not be notified when the Display's "Prompt Pad" property has been enabled.
|
|
9388
|
Screen Objects
|
A Trend in pause mode would move to the initial page each time a pen was selected within the legend.
|
|
9446
|
Screen Objects
|
The Trend's recording functionality, by means of using the "Add Values" variable, would not work correctly and the variable would not reset after having been set to the '1' value.
|
|
9450
|
Screen Objects
|
An Alarm Window or Alarm Banner object connected to a Network Server would not show any errors when the Network Server was no longer available (i.e. when stopped).
|
|
8941
|
Screen Objects
|
In certain cased problems would occur while handling ListBox objects partly overlapping other ListBoxes. ListBox overlapping will now work correctly with the "Show Control Window" option disabled.
|
|
8943
|
Setup
|
The SetUp would install "WWB9@000.dll" file in error which would cause problems displaying dialog windows in Windows 7.
|
|
9021
|
Setup
|
The DEMO projects did not have their Networking Services enabled and therefore could not connect to Web Clients without modifying the projects beforehand.
|
|
8991
|
Setup
|
The SetUp discontinued installing "Movicon.ini" file.
|
|
9041
|
Setup
|
The WinWrap 9.3 version installing warning message did not make sense and therefore has been reworded.
|
|
9502
|
Setup
|
When installing Movicon BA, the "ELAP" driver would also get installed by mistake even though it could not be selected afterwards because not included in the "Drivers.xml" file.
|
|
9511
|
Setup
|
The Movicon BA installation procedures would not install the "GenericDriver.chm" in the Drivers Folder.
|
|
9007
|
Tools
|
The CSVTagIE.exe tool would take too long to import a ".csv" file containing a large number of variables. This procedure has now been speeded up.
|
|
9218
|
Tools
|
In certain particular cases the RestoreFlushedData.exe tool would raise an error when starting up a project.
|
|
7737
|
Tools
|
When using the CSVTagIE, StringImpExp and AlarmsImpExp tools, the import/export procedures would fail if certain characters were used in the texts such as those mapped outside the ASCII table.
|
|
8981
|
Tools
|
Selecting a language for groups and users within the EditUsr.exe tool would also repeatedly show the "bak" language for the same number of languages shown. This was due to selecting the "bak" files of the project's languages in error.
|
|
9048
|
Users Management
|
If the "Run Command after Login" option had been enabled in the Users management, the command would be executed even when the "Access Level" of the user who just logged on did not match the object's "Write Access Level".
|
|
8912
|
WebClient
|
The Java applet would raise an error with a 'NullPointerException' when changing pages too quickly or when resizing the Web client window.
|
|
9235
|
WebClient
|
When opening the same screen twice from WebClient, the screen page would not show in full.
|
|
9340
|
WebClient
|
Loading Grid data from Web Client was rather slow going. The new "WebServiceClientBlockUIOnLoading" registry key can now be set to speed up this procedure. However the user interface will result unusable until the data loading procedure has terminated.
|
|
9331
|
WebClient
|
User Autologoff could no longer be managed from WebClient.
|
|
5384
|
WebClient
|
Scroll bar management from Web Client has been improved in all those objects provided with one.
|
|
9297
|
WebClient
|
When a screen page was displayed from WebClient, it would not load only partly updated if the screen's "Max. Width in WebClient" and "Max. Height in WebClient" parameters had been set.
|
|
66
|
WebClient
|
Scroll bars in special objects such as the Grid and display windows (DataLogger window, Historical Log window etc.) would not show in WebClient. This would happen if the Windows XP theme has not been enabled. If the Windows theme is now disabled, or if the Movicon Server project is run as service (therefore not using the Windows theme), the scroll bars are drawn directly by Movicon (and those from the Windows theme will not be used).
NOTE: however, if a different theme is activated that is not that of "Windows XP", the scroll bars from WebClient may not be as good.
|
|
8983
|
WinCE OS
|
The "ActiveScreen" system variable would not update correctly in Windows CE if screen had been opened as a PopUp.
|
|
9023
|
WinCE OS
|
Movicon would not startup correctly in Windows CE 7 operating systems.
|