- Jason Schultz
- PowerBuilder
- Monday, 2 April 2018 03:13 PM UTC
Hi. We're currently experiencing an issue with a 64-bit .exe created with PB 12.6 Classic (build 4098) running on workstations with Win 10 Fall Creators Update (Build 1709).
The application runs fine on previous versions of Win 7 and 10, and I'm told that it works on a more recent build of Win 10 as well.
Is anyone aware of any known issues between the use of OpenWithParm (passing either a PowerObject or a String) to a response window when running on Win 10 Build 1709? When the code executes, program logic continues immediately and falls through, not allowing for the response window to do a CloseWithReturn (passing back the StringParm or PowerObjectParm).
Aside from troubleshooting with our Production application , I also created a simple application consisting of an application object and a response window. OpenWithParm() doesn't perform as expected on Win 10 1709, but it does on a prior build of Win 10 (Build 1607). Looking for a potential workaround or justification that there is a legitimate compatibility issue with this build. Upgrading to the latest version of PB is not a feasible option right now (perhaps later in the year). Any feedback or insight is appreciated.
Thank You,
Jason Schultz
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.