When The user converts some Proworx projects the resulting Unity application contains extra modules. What can be done?

Goals and Symptoms
The user can see after importing his Proworx32 project to UnityPro that some modules are added. This problem concerns the method used by proworx32
when saving modifications and the process that uses UnityPro to convert Proworx32 files.A Proworx32 file is a file with PWX extension. This kind of file
is in reality an encoded Access 2000 database. The associated Access database can be found in \Proworx\32\Project directory when Proworx32 opens
the PWX file.
When Proworx32 opens a PWX file, it uses mainly a binary table named tbl_ProjectConfiguration to load the module configuration. But when it saves
modification it saves them in tbl_ProjectConfiguration as binary data and in 4 tables (Head, Drop, Rack and Slot) where the data are readable by a user.



Screenshot 1 : Sample of project opened by Proworx32


Screenshot 2: Data tables associated to the initial project


Screenshot 3: Project after conversion and import in UnityPro

As those readable tables seems to be not fully rewritten during each saving phase this generates wrong information (as you can see on Screenshot 2,
there are modules in the table that are not present in Proworx32 –Screenshot 1. These modules are seen by the converter as it uses the 4 user-readable
tables and in consequence these modules are present in UnityPro (Screenshot 3).

Causes and Fixes
In order to correct the Proworx file to have the 4 user-readable tables with good values a manual procedure can be followed:
1 - Open the project in Proworx32
2 - Reselect each rack in the project:



Screenshot 4 : Reselection of first rack



Screenshot 5 : reselection of another rack

3 – Reselect each module in each rack:


Screenshot 6 : Reselection of first module



Screenshot 7 : Reselection of another module

4 – Then force deletion on empty slots



Screenshot 8 : Force deletion of empty slots

5 – Save the project modifications (you could save after each phase)



Screenshot 9 : Save the project

You will see that the first result is that the size of the project file will change:



Screenshot 10 : Project file size change

Opening the Access database associated will show that the tables have been updated:


Screenshot 11 : Slot table in database after modifications

And the result of import the modified project will be similar as the original project in Proworx32


Screenshot 12 : Result of import of modified project in UnityPro

Publikováno pro: Schneider Electric Česká republika