Knowledge Base

Until version 8.00 SP3 (including version 7.20x), PcVue used version 6.2 of Microsoft VBA.

Since version 8.00 SP3, PcVue uses Microsoft VBA version 6.4.

That change gave rise to upward compatibility problems (with ActiveX for instance) as follows.

Situation

• A project is developed with PcVue 8.00 with VBA, using ADO ActiveX .
• When it is started in PcVue 8.00 SP3, it no longer works.

Diagnosis

This is a Microsoft limitation that is found with some ActiveX only. It happens because the VBA project is not loaded and all the application VBA code (associated with mimics etc.) is not loaded either.

The reason is that by default a mimic is saved in binary format. The VBA code includes a COM (Component Object Model) reference to the ActiveX, which is also held in binary. However Microsoft VBA 6.4 cannot read the binary reference of ActiveX saved from VBA 6.2.

Work-around for PcVue

1. Open the project with version of PcVue with which it was developed (e.g. 7.20x or 8.00).
2. Save the mimic in ASCII format.

If required you can change the default options for saving all mimics from Binary to ASCII (in the menu Configure\HMI Options\Files Format\Mimics).

3. Restart the project with version 8.00 SP3 or later
4. Check that its VBA scripts run.
5. The mimics can be converted back to binary format in the same manner if required.

For further information

In the main Help, see the topic Developing the HMI.ActiveX Controls.Saving a Mimic Containing an ActiveX Control In ASCII Format.