Forum Discussion

greg239843's avatar
greg239843
New Contributor
6 years ago

PowerBuilder 2019 classic | MSAA | TC 14.30 cannot resolve objects inside DataWindow

We are thinking about migrating from PB 12.1 to 2019.  We have some tests written in TC.  But TC cannot resolve objects inside Datawindow. Using Object Spy, we can't targer edit columns or DDDW/DDL...
  • TanyaYatskovska's avatar
    TanyaYatskovska
    6 years ago

    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.

     

     

TanyaYatskovska's avatar
TanyaYatskovska
SmartBear Alumni (Retired)
6 years ago

Hi greg239843,

 

According to the article you mentioned, TestComplete 14.30 supports the following PowerBuilder version:

12.0, 12.5, 12.5.2 and 12.6.

Is v.2019 newer than 12.6?

 
  • greg239843's avatar
    greg239843
    New Contributor
    6 years ago

    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. 

    • TanyaYatskovska's avatar
      TanyaYatskovska
      SmartBear Alumni (Retired)
      6 years ago

      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.

       

       

      • greg239843's avatar
        greg239843
        New Contributor
        6 years ago

        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.