AFAIK, all of the different versions of VPE (and all of the external function declarations I've seen) use the same function names, so if you included a StarZen's VPE code, all of the DLL functions would be defined for the DLL for that version of VPE. When the compiler sees the same function names declared in VPE71.pkg that generates an error.

It might work to change all of the external function declarations to include the VPE version # in the DF function name that is mapped to the DLL function. e.g. instead of

Code:
External_Function32 VpeOpenDoc "VpeOpenDoc" VPEDLL Handle hWndParent  String title  Dword flags Returns Dword
do this:

Code:
External_Function32 VpeOpenDoc71 "VpeOpenDoc" VPEDLL Handle hWndParent  String title  Dword flags Returns Dword
But then you'd have to change the code base to use the revised function names.

There are similar issues with Sture's VDF Query (I just comment out the use statement for the file with the VDF Query VPE function declarations IIRC).