xA 5.1 64Bit: Experiances with VB grafics form xA5.0?
Can someone give comments or share experiances on VB behavior for xA 5.1 64Bit System, new screens PG2, existing ones VB.
I know of a application that were up-graded from 5.0 to 5.1 revA by keeping the VB screens, Operator workplace freesed. Sporadic deadlocks, PC blocked.
Affected were Workstations with 2 or more screns. cause is on MS OS.
Who has experiances under which circumstances there are no issues with existing VB grafics from 5.0 in 5.1?
Under which circumstances VB will not work under any circumstances?
From on which xA Version existing VP screens will not be programmable anymor?
Voted best answer
One of the main reasons wht its recommended to use PG2 is beacuse Microsoft has stopped support for Visual Basics. Please check if you have done the following during the upgrade from 5.0 to 5.1.
• Installing Visual BASIC 6.0 with SP6 must be followed for all nodes that use Graphics Builder and the Primary Aspect Server node. This must be done before performing the procedures under Perform the 800xA System Restore.
• Installing the VB Graphics Extension Software must be followed for each VB Graphics extension software package on all nodes in the 800xA 5.1 System, if the base product was installed on the 800xA 5.0 SP2 System. This must be done before performing the procedures under Perform the 800xA System Restore.
• Load the VB Graphics extensions on the Primary Aspect Server.
Process Graphics and the VB based process graphics can co exist in parallel in the same system.If the VB graphics extensions are loaded the user can still program the VB gaphics.
VB will not work under any circumstances if 3rd party components (OCX) that have been used to build screen graphics is incompatible with Windows 7.
Also, the VB screen will not work in 800xA 5.1 in case of some logic exist written on Visual Basic, beside the standard "iif" conditions (e.g. if you have a timer subroutine).
You must have a warning message about it when you trying to open such screen for editing in VB.