You'd have to test your application thoroughly to say whether it runs or not. Any issues would probably be specific to your environment so a blanket yes or no isn't possible.
PowerBuilder 2022 is the first version to officially support Windows 11. PowerBuilder 2017 R3 has already passed End of Mainstream Maintenance (EOMM). It will be EOL July 31, 2025.
You should consider migrating to PowerBuilder 2022.
Hi Roland, thanks for the response. I understand what your saying and I do know about the dates. I am just seeing if I can buy some time.
I have not been able to get PB2017r3 OR Infomaker 2017r3 to work in windows 11. Does not even open, crashes right out of the gate. So I was just wondering if it even can run under windows 11 before I spend time trying to figure out why it does not. PB2017 (No release) actually opens but 2017r3 does not.
Hi Roland, thanks for the response. I understand what your saying and I do know about the dates. I am just seeing if I can buy some time.
I have not been able to get PB2017r3 OR Infomaker 2017r3 to work in windows 11. Does not even open, crashes right out of the gate. So I was just wondering if it even can run under windows 11 before I spend time trying to figure out why it does not. PB2017 (No release) actually opens but 2017r3 does not.
Hi Chris, we will be moving to the newest PB. But it will take time to convert and test so I am trying to just determine if PB2017r3 runs under Win 11. If it does not then I can keep my developers temporarily on win 10, support and deploy apps to win 11 while we start the process of going to the newest PB. I have had no luck trying to run PB2017R3 under win11 so I was just trying to find out if it even works/runs under win11 so that I don't waste a lot of time trying to get it to run under win 11. I am surprised at how a simple question has gone in so many directions except just the simple yes/no answer I was hoping to get.
Hi Roland, did not want to get that far yet. I was just making sure that it could run under win 11 first before spending time looking into it. It turns out we found the problem. The person setting up the PC had done it incorrectly and we ended up with multiple copies of some of the PB dll's. Once we eliminated the duplicates PB started with no issues. Unfortunately the daunting task of upgrading from 2017 to 2022 will be an interesting ride.
The person setting up the PC had done it incorrectly for a developers pc (vs a users pc) due to this we ended up with multiple copies of PB dll's. Not only were there DLL's in the normal PowerBuilder directories but they were also installed into the windows\system directory. When using windows event viewer I noticed the dll and location of the error which we knew for a developers machine they should not be there. Once we eliminated the duplicates, PB started with no issues.
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.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.
We (>60 Developers) have used PB2017R3 on Windows 11 since it was released, we never had such issues.
Regards, Simon
Andreas.