VB to PG2 Migration
1) Any tool exists for converting the VB faceplates to PG2 even if the libraries are in released state?
Any suggestions Pls..
I would not retain the same library version digits after a PG2 conversion. After Windows XP comes Windows 7, after VB6 comes PG2... a new version number is recommended to indicate that something has changed.
You can easily make a new (open for editing) version of any open, closed or released library and perform your changes there. A Control IT application or library can be protected with a password to prevent unauthorized changes, reverse engineering and theft of intellectual property.
However, this protection mechanism only protects the parts engineered inside Control Builder M, not VB6/PG2 graphic aspects engineered in Plant Explorer/Graphics Builder.
I also believe you can add new PG2 aspects to an already closed/released library. The new aspects will not become members of the library, but still be visible and inherited to the object type instances. Also, it is possible to put custom stuff in Extension Libraries, in fact this is utilized in standard libraries for AC 800M, one ext lib for VB6 and another for PG2.
If the library was purchased from 3rd party, etc. I sincerely recommend asking the vendor for a PG2 version of the library, otherwise your "bootleg" version risk to conflict with the bona fide version - and what do you tell your customer? "I have provided you with a 'custom' version of O&G's REUSE library to a 10th of the real library price"???