• You are here:  
  • Home
  • Q&A
  • Q&A
  • Beta Testing
  • PowerBuidler 2025 Beta - Menu has errors even though source is the same

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

Resolved PowerBuidler 2025 Beta - Menu has errors even though source is the same

  1. Issue
0
Votes
Undo
  1. Tom Peters
    Tom Peters
  2. Beta Testing
  3. Thursday, 17 October 2024 12:57 PM UTC

Good Day!

I am trying to migrate my PB22 R3 source to PB25 Beta. I consistently get this error:

---------- Compiler: Errors (8:51:31 AM)
pfemain.pbl(m_master).m_.Forward Declarations.183: Error C0031: Syntax error
---------- Finished Errors (8:51:31 AM)
---------- Elapsed: 00:00.302

When I do a DIFF between what's in my PFEMAIN versus what's in my SCM, it shows no differences. I have tried restoring my source and re-migrating. I have even fully rebuilt my PBLs into PB22 R3 and then tried migrating again. Same issue.

Now, full disclosure; Yesterday I was able to open my PB22 R3 source in the PB25 IDE and the migration worked. Things seemed to start going sour once I tried to rebuild my PB25 source using Orca and PBAutoBuild with the /pbc switch. I cannot confirm this is the issue because, as mentioned, I have fully restored all my source to PB22 R3 and tried migrating using the PB25 IDE. Same errors over and over, even though the source is the same.

Is there some setting in PB.INI or my Registry I need to reset?

Thanks,

Tom

  1. PowerBuilder (Appeon)
Use of PBD files in Solution mode
RibbonBar ButtonImage property seems to require fu...
Responses (3)
Tom Peters
Tom Peters Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 15:32 PM UTC
  2. Beta Testing
  3. # 1

Ugh... I'm an idiot

 

I do not recall doing this, but I must have unchecked the Allow dashes in identifiers. I do not recall doing it, but I noticed all the failed objects have dashes. It would have been nice if the error message indicated a bad name or something, but I admit the problem is between the chair and the keyboard. 

 

Thanks for your time. Sorry

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 21 October 2024 19:18 PM UTC
Thanks for sharing the solution Tom!
  1. Helpful
kitty he @Appeon
  1. kitty he @Appeon
  2. Tuesday, 22 October 2024 02:23 AM UTC
Hi Tom,



Are you referring to the "Design -> Script -> Allow dashes in identifiers" option in the IDE? AutoBuild should be able to run independently of the IDE, so theoretically, it shouldn’t be affected by this option. Could you please provide a small example that can reproduce the issue? I’ll look into it and see what might be causing the problem.



Regards,

Kitty

  1. Helpful
Tom Peters
  1. Tom Peters
  2. Tuesday, 22 October 2024 17:37 PM UTC
Hey Kitty -

Yes, that's the setting. When that switch is off, the following fail:

1. migrating source from PB22 R3 to PB25

2. OrcaScr250 IMPORT



Now, if I do a clean migration with that option checked, then I uncheck it, close the IDE and use PBAutoBuild as PBC, the rebuild fails. It does feel like Auto Build, at least when using the /pbc switch, does in fact look at my IDE settings.



Thanks,

Tom
  1. Helpful
There are no comments made yet.
Tom Peters
Tom Peters Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 12:21 PM UTC
  2. Beta Testing
  3. # 2

Hi Kitty -

The only coding changes I made pertained to an instance variable we use to ensure only the correct UI version connects to a corresponding DB version of our product. I turned on the RibbonBar on our m_frame. Everything was working.

Then, I tried converting to a Solution and it failed spectacularly. I decided to forget the solution end of things and go back to a workspace. I deleted the entire folder, copied my clean source to another (new) folder, and tried migrating again. I have done this numerous times and it fails every time, now.

Thanks,

Tom

Comment
There are no comments made yet.
kitty he @Appeon
kitty he @Appeon Accepted Answer Pending Moderation
  1. Friday, 18 October 2024 03:16 AM UTC
  2. Beta Testing
  3. # 3

Hi Tom,

 

  1. From 2022 R3 to 2025, did you do anything between the initial failure and the first success?
  2. After successfully migrating to 2025, what specific actions did you take that led to the code issue?
  3. The settings for the INI file and registry items should not need to be changed.

 

Please submit a bug report to help us record and track the issue.

https://www.appeon.com/standardsupport/newbug

 

Regards,

Kitty

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 21 October 2024 13:48 PM UTC
Hi Tom;

Since this seems to be a PFC issue as well. It might be worth reporting this on the PFC website. My STD Framework ports with no issues. Build 3391 beta is actually my 3rd beta. I've had no App solution conversion issues on any of my testing thus far. So it might be worth approaching this problem from both angles. Just a suggestion.

Regards .. Chris
  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.