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

Resolved Unknown Function Name Error for Unknown Reasons

  1. Advice
0
Votes
Undo
  1. Keeley Stalnaker
    Keeley Stalnaker
  2. PowerBuilder
  3. Wednesday, 13 April 2022 17:00 PM UTC

Hi;

Basically, I am trying to make a copy of a PB app and having issues. (PB192)

I made a new workspace and target, added the pbl from my old app, and tried to deploy with incremental build without changing anything other than pasting in the open/close events and global variables from the old app into the new application object. When I try to deploy, I am getting an unknown function name error (C0051) for every external function that's declared in the transaction object. It is only one pbl and if I go back and try to deploy the old version, it is fine. Where have I gone wrong?

Thanks!

Hex code for Transparent background of statichyper...
PB 17 & 19 : Error Checkin "Paramètre Non valide"
Accepted Answer
Arnd Schmidt
Arnd Schmidt Accepted Answer Pending Moderation
  1. Wednesday, 13 April 2022 18:57 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Keeley,

you have to declare your transaction object as the default global object for SQLCA.

Check the additional properties of your application object.

https://docs.appeon.com/pb2019/pbug/ch04s04.html#Specifying_default_global_objects

hth

Arnd

Comment
Keeley Stalnaker
  1. Keeley Stalnaker
  2. Wednesday, 13 April 2022 19:06 PM UTC
Yesss that is totally it. Thank you!
  1. Helpful
There are no comments made yet.
Responses (3)
Keeley Stalnaker
Keeley Stalnaker Accepted Answer Pending Moderation
  1. Wednesday, 13 April 2022 18:01 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris;


Thanks! I should have mentioned that the external functions are declared in the transaction object in the pbl so they are still there. Some reference global variables which I have copied over to the new application object so those are still there too.

Comment
Load more comments
Keeley Stalnaker
  1. Keeley Stalnaker
  2. Wednesday, 13 April 2022 18:13 PM UTC
Yes. I am 99% sure the issue is operator error, just haven't figured out in what way. lol.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 13 April 2022 18:31 PM UTC
Sounds like you might not be pointing to a DBMS instance based on your current DB Profile where those RPC's are declared and thus, are checked at compile time? Could that be the case?
  1. Helpful
Keeley Stalnaker
  1. Keeley Stalnaker
  2. Wednesday, 13 April 2022 18:41 PM UTC
I did check that as well so I think it had to do with using a new workspace and adding a new target when I really just needed to add a second application... or something like that. When I copied over the old workspace and just added a second application it compiled fine. My major concern was just not having pbls named the same as the old app so they can run concurrently, so I will probably just manually edit my pbl name and library list and keep it moving.



Thank you as usual for your speedy assistance!
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 April 2022 17:13 PM UTC
  2. PowerBuilder
  3. # 2

Hi Keeley;

  Most likely it's because the external function declarations are defined globally vs instance of an object. Thus, global external functions are tied to the Application Object. If that is the case, then creating a new App Object would then be missing all the external function declarations.

Regards ... Chris

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