Forum Discussion
Hi Tanya
2019 is newer than 12.6.
After 12.6 from like 2012 (12.0 was from 2008), next was PB 2017 and now there is 2019.
I can see that You support only "up to 12.6". But if You use MSAA API then it should just work. Someone changed something :) Or there is some special code in TestComplete to enable PowerBUilder support.
Thanks for the update. I think the best option will be to submit this query to the TestComplete Support Team. They can work with our R&D team to investigate how TestComplete 14.30 can work with PowerBuilder 2019.
- greg2398436 years agoNew Contributor
Well, there is the question about TAM (Total Adressable Market) for TC and PB2019.
I think it is around like 00001.34$ :)
So if SmartBear needs to spend >1.34$ to fix it...
I was just asking "Community", maybe there is some hidden checkbox that will resolve this problem.
Maybe we just need to move some DLL file and it will start working again.
Maybe You must add "PBACC190.DLL" (and PBACC170.DLL) to TC code to enable MSAA support in PB2017/19.- TanyaYatskovska6 years agoSmartBear Alumni (Retired)
Hi greg239843,
It's worth contacting the Support Team anyway. They need to make sure that this version is tested in our test lab. Perhaps, it's an easy fix. I'm sure they will find a solution.
- Kumaran15 years agoOccasional Visitor
Hello All,
After upgrading from PB 2017 to PB 2019 we have following issue. I saw in the mail thread that Testcomplete also faced the similar issue. Any workaround to get this issue resolved ?
The issue is Robotic applications like UIPath does not seem to select individual fields when it opens our application that is on Powerbuilder 2019. It was able to do it when the application was on Powerbuilder 2017. With the application on 2019, their Robotic application currently is able to select the entire datawindow painter rather than the individual fields within the datawindow. They are able to select individual SLE’s(Single Line Edit) with in the window without any issues. The issue is mostly with individual columns in a datawindow.
that prevents these kind of external robotic applications from accessing individual datawindow fields, when they were able to do it successfully when the application was on PB2017.
Regards
Kumaran KS
Related Content
- 10 years ago
- 5 years ago
Recent Discussions
- 4 days ago
- 4 days ago
- 8 days ago