1. John Brown
  2. PowerBuilder
  3. Thursday, 29 April 2021 15:56 PM UTC

All -

I apologize if this isn't the forum.  Hard finding answers for 12.6 related issues these days.

We currently have a 12.6 application running on Citrix box ( 2016 server ).

We have ONE user that recently switched to a new windows 10 laptop.

When they connect to Citrix ( via web url ), they can run Citrix, and run the application.


Some screens don't respond to her mouse - can't click dropdowns, some buttons.


We haven't made any code changes in a long time.

I was wondering if anyone else has seen similar behavior, either in older environments or more recently?  Ideas to troubleshoot?


Thanks all,

- John

Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 29 April 2021 19:56 PM UTC
  2. PowerBuilder
  3. # 1

John -

1) Citrix:  this is a known issue with PBv12.x running on any version of Citrix Receiver after 4.9.
   Note that the same code compiled with PB2019R3 >>> will <<< work on the newer Citrix receivers.

2) Who made the decision to leave PowerBuilder without having a target technology specified? Sound like pointy-haired management to me.

3) I'd be interested in hearing which technology will be used to replace PB. I've never yet heard of a single instance of any tech replacement for PB a) coming in on time, b) on or under budget, OR c) delivering a replacement that has all the features provided by the PB application. I've never heard of a replacement that handed in all three of those attributes.

   Meanwhile, I've heard and read hundreds of stories where replacement tech, usually Java or some flavor of C, costs a fortune, goes WAY over schedule, and fails in the end.

3) One more item to note: the new PowerBuilder allows all kinds of coolness, including converting the code into C# with what they call their "Snapdevelop" tool. Being a PB product, this means you still get to keep the mighty datawindow.

Disclaimer:  I have not personally used Snapdevelop so I might have a detail wrong here.

  1. Armeen Mazda @Appeon
  2. Thursday, 29 April 2021 20:09 PM UTC
Hi Olan, You are exactly right that if you are going to migrate PB apps to different language then SnapDevelop is the way to go. The C# code it generates can be maintained in any C# IDE, but many customers prefer SnapDevelop over Visual Studio because of its code generation capabilities and integrated Web API tester.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 29 April 2021 17:38 PM UTC
  2. PowerBuilder
  3. # 2

Hi John,

Please take a look at Miguel's answer in this post: https://community.appeon.com/index.php/qna/q-a/script-window-and-mouse-wheel

It is related to scroll issue of the PB IDE rather than PB app, but it might also work for your situation.  I suggest you try.

Another thing you may want to consider when you upgrade is deploy your app using PowerServer so you can throw Citrix in the trash: https://www.appeon.com/products/powerserver

Best regards,

  1. John Brown
  2. Thursday, 29 April 2021 17:45 PM UTC
Thanks, Armeen!

A couple things here .... It's not an issue with scrolling.

When you just click the mouse button : on a window button or a down arrow of a dropdown on a window item, nothing happens. It's also only one user. We're not seeing this anywhere else.

Additionally, our company looked at PowerServer and decided not to go with it. They plan to replace the PowerBuilder applications in the future with another technology.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Thursday, 29 April 2021 17:49 PM UTC
Oh, I see. Then Miguel's solution is probably not going to resolve your issue.

The new PowerServer is completely revamped from the version you tried before, but if decision already made I understand.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 29 April 2021 16:02 PM UTC
  2. PowerBuilder
  3. # 3

Hi John;

  FWIW: You are always welcome to post general PB questions on any version of PB in this forum!

  FYI: PB 12.x releases were not W10 compliant. This was only achieved in Appeon PB 2017 and higher.

        My suggestion would be to download a trial version of Appeon PB2019R3 and then compile your App with that release and see if that cures the W10 user's App issues.

Regards ... Chris

  1. John Brown
  2. Thursday, 29 April 2021 16:15 PM UTC
Chris - thanks for the reply! We currently have Appeon 2019 in house and are in the effort of migrating our applications. We just haven't been able to get them out to production. Still going through testing.

We were just trying to see if there was a quick, hopefully simple, solution to this very odd issue we're seeing.

We've been running the PB12 stuff in Windows 10 for quite a while without incident. I know PB can be picky and hyper sensitive ( been fighting with it since 1995 ).

Thanks for the reply!

- JB
  1. Helpful
  1. Chris Pollach @Appeon
  2. Thursday, 29 April 2021 17:08 PM UTC
FWIW: I have encountered the odd issue too in the newer W10 O/S versions. I am currently on W10 20H2 build 19042.928 and have have for example DDE issues (broken in 20H1 but fixed OK now in 20H2). So sometimes it's not PB but Microsoft jerking the chain. ;-)
  1. Helpful
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.