1. Sally D
  2. PowerBuilder
  3. Tuesday, 20 November 2018 09:14 AM UTC

Hi all

When i migrate the PB12 to PB17, the system error occurs when use inherited. "Bad runtime function reference at line...", this error just occurs sometimes, how could we fix this? Seems the error doesn't related to code. Do you have any ideas about this error?

Olan Knight Accepted Answer Pending Moderation
  1. Wednesday, 21 November 2018 05:15 AM UTC
  2. PowerBuilder
  3. # 1

When I run into this here's what I do:

1. Isolcate your code into a new, separate folder. VERIFY that you have all of the expected PBLs.
2. Create a new workspace, and a new target.
3. Do a full build.
4. Run the code.

If it barfs at this point with the "Bad runtime reference" you will need to open the code in DEBUG mode and just step through the open process until you find the error. As has been stated, this error is clear cut - you're missing an object or a function or an event in an existing object.

 

Good Luck,

Olan

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

Hi Sally;

   Is this a PFC based App?

Regards ... Chris

Comment
  1. Sally D
  2. Wednesday, 21 November 2018 01:52 AM UTC
Hi Chris,

Yes. PFC based App
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 21 November 2018 14:46 PM UTC
Hi Sally;

When you migrated to PB2017 from PB12.x - Did you replace the PFC layer with the PB2017 version of the PFC?

FYI: https://github.com/OpenSourcePFCLibraries/2017

Regards ... Chris
  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 20 November 2018 14:50 PM UTC
  2. PowerBuilder
  3. # 3

That can happen when you use the Dynamic keyword and the function called doesn't exist at run time.

Comment
There are no comments made yet.
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Tuesday, 20 November 2018 14:21 PM UTC
  2. PowerBuilder
  3. # 4

Hi Sally

I think were going to need some more information. "Bad runtime function reference at line..." would normally point to where the error occurs, but you say that this is not the case?

Are you sure that the system error event is reporting the correct information? If it is then I would suggest taking another look at the reference it is referring to and ask does the object involved exists. What state is the application in when the error occurs and what happened immediately beforehand. Was the user closing a window or something else?

Anyway if you could share the exact error and the code it is referring to I would be happy to put my mind to the problem.

Cheers

David

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.