To port from version 3, 4, or 5  to version 6 follow these instructions.  

NOTE: the most common call we get regarding porting is solved by making sure to update "PE4API.BAS" or"PE5API.BAS" to "PE6API.BAS" so DLL declarations point to the correct DLL. Double check any Declare statements in your project.

Using VBPORT:

1. Back up your current project.
2. Run the VBPORT utility from the Start / ProEssentials6 / VBPORT menu.
3. Use the [Browse] button to open a VBP or FRM file belonging to your project.
4. Click the Start Port button. The file is adjusted by replacing references to v3/4 ActiveXs with references to v6 ActiveXs. The old file is renamed by appending BAK to the file name. The filename ported is added to the history list to make it easier to keep track of whats been ported.
5. Continue opening and porting until all FRM files are ported as desired.
6. Now when you open the project in VB, the project will use ProEssentials v6 ActiveXs.

To port from version 2 or earlier to version 6 follow these instructions.

Manually Porting :

1. Back up your current project and open project in design mode.
2. Go to any forms which contain ProEssentials OCXs and delete the controls off of the forms. Make a note of the Name property. Don't worry about your code, it will remain.
3. Save the Project.
4. Go to Components Dialog box and de-select the v2 or older OCXs and select the new v6 OCXs. The new v6 OCXs will have "v6" at the end of their description or have the letter "c" after the OCX name like PEGOC.
5. Go back to any forms where the older OCXs were deleted and reinsert the new v6 OCXs. Rename the controls as needed and save the project.

You may need to port Class Modules and User Controls manually as needed.

Related to Porting!

Printing Logic Needs Changing!

The addition of clipping logic has the potential to break current ProEssentials implementations which include custom printing logic. In the process of porting an application to v6, you should plan on changing calls of PEresetimage to PEresetimageEx or disabling clipping by setting DisableClipping to TRUE.

Note that if your project calls PlayMetafile with respect to low-level printing, it should now call the ProEssentials function PEplaymetafile.

Custom Parameter Set now Disabled!

NoCustomParms is now by default set to TRUE. If desired, set this property back to FALSE.