QTP 11 recognizes Powerbuilder 12.5 objects as Windows objects

Category:
Question ID: 104523
0
0

I’m automating an Powerbuilder 12.5 app. I’ve applied all of the different patches to QTP 11, but when I object spy the powerbuilder app, QTP still recognizes the objects as (for example):
Window("Window").Window("Application Logon").PbDataWindow("PbDataWindow")

Shouldn’t QTP return PbWindow("Window").PbWindow("Application Logon").PbDataWindow("PbDataWindow")?

Marked as spam
Posted by (Questions: 1, Answers: 1)
Asked on May 28, 2012 10:28 am
6 views
Answers (6)
1
Private answer

Can you list what patches you have installed? QTP has release patch QTPPB_00034 - Support for PowerBuilder 12.5 Applications

Have you run a repair to QTP [(See this link for procedure)][1]?

[1]: http://eyeontesting.com/questions/1103/repair-qtp-11-with-out-media/1104

Marked as spam
Posted by (Questions: 2, Answers: 98)
Answered on May 30, 2012 5:11 pm
0
Private answer

Installed patch QTPPB_0034. Didn't seem to do anything. I followed the instructions on the link. Nothing has changed.

Marked as spam
Posted by (Questions: 1, Answers: 1)
Answered on May 31, 2012 12:27 am
0
Private answer

I found out the issue. With QTP open...if I opened the app, QTP would only recognize the objects as Windows objects not PowerBuilder objects. If I run the System.Util Run line to open the app, then QTP will recognize all of the PowerBuilder objects. I don't know if that's normal. Maybe I installed a patch wrong or something, but that's where I am. It works if I allow QTP to open the app. Have you ever heard of something like that?

Marked as spam
Posted by (Questions: 1, Answers: 1)
Answered on June 4, 2012 9:47 am
0
Private answer

I found out the issue. With QTP open...if I opened the app, QTP would only recognize the objects as Windows objects not PowerBuilder objects. If I run the System.Util Run line to open the app, then QTP will recognize all of the PowerBuilder objects. I don't know if that's normal. Maybe I installed a patch wrong or something, but that's where I am. It works if I allow QTP to open the app. Have you ever heard of something like that?

Marked as spam
Posted by (Questions: 1, Answers: 1)
Answered on June 4, 2012 9:47 am
0
Private answer

I have the same issue. Did find out what caused this issue and how to fix it?

Marked as spam
Posted by (Questions: 0, Answers: 1)
Answered on June 18, 2013 12:58 am
0
Private answer

Check in Automation->Record and Run Settings if it's configured to work only on apps opened by QTP. If so, then the behavior you've decribed is normal.

Marked as spam
Posted by (Questions: 0, Answers: 1)
Answered on May 12, 2014 2:48 am