Most of the objects in the PFC**** libraries inherit from an object in the PFE**** libraries. There are likely some objects missing from your PFE layer. Look at the standard PFE libraries and copy over the ones you are missing.

Well guys,

I think I'm waving the white flag on this attempt to move to the newer PFCs.  After I finally figured out what to do (I hope), I'm getting compile errors within the new PFCs and I don't know how to correct them.  This is a cherry-picked handful or errors that I believe are related:

PFCMAIN.PBL(pfc_u_dw).35: Error       C0001: Illegal data type: n_cst_dwsrv_grid
PFCMAIN.PBL(pfc_w_master).15: Error       C0001: Illegal data type: n_cst_winsrv_style
PFCDWSRV.PBL(pfc_n_cst_dwsrv_grid).pfc_n_cst_dwsrv_grid.of_showdialog.50: Error       C0015: Undefined variable: w_grid
PFCDWSRV.PBL(pfc_n_cst_dwsrv_grid).pfc_n_cst_dwsrv_grid.of_showdialog.55: Error       C0094: Routine must return a value.
PFCDWSRV.PBL(pfc_w_grid).pfc_w_grid.open.51: Error       C0194: Missing pcode block for indirect function. Possible cause: library missing from library list.

I think I may just settle for using the older PFCs with the newer DLLs that I found were required for PB2017 and go from there. My apps are working with that combination.  I've spent too much time on this already.

regards,
Jim

This warning message has been happening for many versions. It would seem to me that if they actually made the change to make local structure variables private, the warning message should have been removed or reworded to say that they are implicitly private.

It won't cause any issues but it would be a good idea to get the latest PFC version.

I suspect your existing PFC libraries have been migrated several times over the years, as the os_cachelist object structure was replaced by the pfc_n_cst_dwcacheattrib/n_cst_dwcacheattrib non-visual objects in version 7, according to documentation comments in the current libraries.

Definitely time to refresh your copy of the PFC/PFE libraries.

Thanks for the input, Chris,

So, someone else suggested a move to the PB 2017 version of the PFC libraries for a different issue. 
Where are they?  The ones suggested were stored on a non-Appeon server and created by one of the Community Experts.

I would have expected there to be "official" PB2017 PFC libraries provided by Appeon.  Are there?  Where are they?

Thanks,

Jim 

Hi Jim;

   Sounds like the compiler complaining about duplicate instance variables. If it encounters this situation, that message can appear.

   I suspect that the way to get rid of these issues will be to adopt the PB 2017 version of the PFC libraries. Sounds like your trying to migrate your old PFC objects from the 11.x era - which could be even older than that release. Such old PFC's could certainly give you such issues.

     Hopefully, your PB developers did not modify of your current PFC layer objects. Only the ones in the PFE layer.

Regards ... Chris