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

Resolved EditSource Error

  1. How-to
0
Votes
Undo
  1. Olan Knight
    Olan Knight
  2. PowerBuilder
  3. Tuesday, 10 September 2019 14:17 PM UTC

PB v12.1, build 7055
Window 7, 64 bit platform
PNB Classic application

I have a tabpage.
It was working great. I exported it to SAVE the work.
I did an EDIT SOURCE on the tabpg. DId not loke the result. Exited.
When I attempt to import the SRU that I exported earlier, I get the following error:

icabs_cfg.pbl(u_cfg_tabpg_tier_levels).35: Error       C0176: Badly ordered TYPE and VARIABLE declarations. Is this modified exported source?

Say WHAT?

What does "Badly ordered TYPE and VARIABLE declarations" mean?
Anyone know how to track this error down?


Thanks,

Olan

How to accurately output the content in DataWindow...
Time taken for SetFullState(lb_ret)
Responses (4)
Bernhard Stoeter
Bernhard Stoeter Accepted Answer Pending Moderation
  1. Tuesday, 10 September 2019 14:51 PM UTC
  2. PowerBuilder
  3. # 1

Very old bug in all(?) PowerBuilder versions including PB 2019.

Try to import the exported source into another pbl and move it to it's original place.

Bernhard

Comment
Olan Knight
  1. Olan Knight
  2. Tuesday, 10 September 2019 16:36 PM UTC
Thanks, Bernhard. I had never seen this before.



Olan
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 10 September 2019 16:37 PM UTC
  2. PowerBuilder
  3. # 2

Since I had the original EXPORT file, I was able to recreate the object by starting over.

First, I saved the original export file into a different file, then I opened that new file in Notepad++.

Next, I would add an object, save and regenerate, open in EditSource mode, and replace the object definition with the definition from the saved export file in Notepad++. Save the object, regenerate, and export it to save my work.

I repeated step 2 until all objects were created, then restored all the functions, then all of the events.
Save. Regenerate. Export.


Yeah, it was kind of ugly, but it worked and I now have my object that took a week to create back in working order.


Thanks,

Olan

Comment
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 10 September 2019 18:15 PM UTC
  2. PowerBuilder
  3. # 3

Hi, Olan -

If you inspect the beginning portion of source code from several windows or user objects via Edit Source, you might notice the pattern whereby object type declarations always precede declarations of variables/objects. This makes sense, as the compiler needs to identify an object's type before it can work with a variable/object of that type.

I think in your case the compiler found one or more VARIABLE declarations prior to seeing the TYPE declarations, resulting in the "What do you expect me to do with this mess you are importing?" message you received during the attempted object import.

Stupid compiler! It should just KNOW what is meant!!! wink

I'm glad you were able to eventually restore your object.

John

Comment
There are no comments made yet.
Donald Clayton
Donald Clayton Accepted Answer Pending Moderation
  1. Tuesday, 14 May 2024 14:18 PM UTC
  2. PowerBuilder
  3. # 4

Hi Olan,

Did you happen to compare the completed object to the original and figure out what PB was actually complaining about?

Regards,

Don

Comment
Load more comments
Olan Knight
  1. Olan Knight
  2. Tuesday, 14 May 2024 17:19 PM UTC
Hi guys!

Donald: I did not, I am sorry to say. I got them working then moved on to the next issue.



John: You are correct! I retired on 02-NOV-2022, the day after my company decided to stop supporting the main product for which I was responsible. Oh, they were making profit on it, like $6M+ per year, but that "wasn't enough profit" to make it worth while continuing to support!?! This, of course, after having offshored the support for the product. (Maybe I'm just cheap, but 6 megabucks a year sounds like a decent profit to me!)



Anyway. At first I was truly annoyed at the idiots in management, but my severance package was excellent and I had been experiencing Short Timer's Disease for a while. I paid off my house, had and have a goodly amount in my 401K (thank the Heavens!), and after a couple of weeks I relaxed into Not Working and decided that the layoff was a Blessing In Disguise! I am now VERY happily retired!



I do miss this Forum and the people with whom I interacted regularly (and semi-regularly), but not working with PB daily means that I'm really out of the action, and my skills have seriously dulled with non-use. Meanwhile, I wish everyone here the very best!



Who knows? I might get back into PB in the future! All the best, everyone!
  1. Helpful
John Fauss
  1. John Fauss
  2. Tuesday, 14 May 2024 17:46 PM UTC
We appreciate the update and hearing from you, Olan! Congratulations on your retirement. It's very likely that I will also be making the transition in the near future, but I hope under better circumstances than what you experienced. I'm very glad everything is going well for you.
  1. Helpful
Donald Clayton
  1. Donald Clayton
  2. Wednesday, 15 May 2024 12:00 PM UTC
Congratulations, Olan, wishing you all the best.

Don
  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.