• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Cannot assign object of type n_cst_platformunicode to variable of type n_cst_platformwin32 at line 8 in function of_setenabled of object nep_n_cst_dwsrv_printpreview.

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Cannot assign object of type n_cst_platformunicode to variable of type n_cst_platformwin32 at line 8 in function of_setenabled of object nep_n_cst_dwsrv_printpreview.

  1. Issue
0
Votes
Undo
  1. Anton van der Post
    Anton van der Post
  2. PowerBuilder
  3. Tuesday, 6 March 2018 20:45 PM UTC

I am running in the following error - after migration from PB9 to PB2017 R2

Message Title
PowerBuilder application execution error (R0023)
Message
Application terminated.
Error Cannot assign object of type n_cst_platformunicode to variable of type n_cst_platformwin32 at line 8 in function of_setenabled of object nep_n_cst_dwsrv_printpreview.

Not sure how to solve this ...

Any pointing in the right direction and/or example(s) - is appreciated.

Thank you,

Anton

  1. Error
Installation Scripts
Appeon Mobile - Package Wizard - Missing Libraries...
Responses (2)
Arthur Hefti
Arthur Hefti Accepted Answer Pending Moderation
  1. Wednesday, 7 March 2018 04:30 AM UTC
  2. PowerBuilder
  3. # 1

Hi Anton

simply changing the PFC won't fix your problem. In your extension object nep_n_cst_dwsrv_printpreview you have to change the variable for the platform from n_cst_platformwin32 to n_cst_platformwin. f_Setplatform creates the variable type based on the environment.

Regards
Arthur

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 6 March 2018 20:56 PM UTC
  2. PowerBuilder
  3. # 2

Hi Anton;

  Yes, the PB 9 compiler was tightened up a lot since V9.x in the 10 thru 12.6 versions of PB. Not only that but the PFC was tweaked quit a bit in the 10.x versions to also accommodate not only this type of issue but also to adjust for the Unicode realm (which PB >=10.0 is Unicode).

  Instead of migrating the PFC from whatever version you were using in PB 9.x, I would strongly suggest that you replace the PFC layer (not PFE layer) with the latest version of the PFC from GitHub to correct this issue and even more potential issues from using the old ANSI version of the PFC.

HTH

Regards ... Chris

Comment
Anton van der Post
  1. Anton van der Post
  2. Tuesday, 6 March 2018 21:44 PM UTC
Thank you for your response - will have to dive into the PFC layer....



Anton



 

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.