Hi Ken;

  FWIW: PB 12.6 was a poor release for SAP as it had "tons" of MR's and EBF's for a few years after its release to try and stabilize it and fix various regression bugs. Plus as John pointed out, it's a deprecated release now and no longer has any support since 2017.

  My suggestion is to think about downloading an Appeon PB release and then look at migrating your PB 12.1 Apps to one of these supported releases (PB2017 R3 or PB2019 R2). Just my $0.02.

Regards ... Chris

try to move all the code of the open event to an event that is called with POST from the open event.

see what happens. It's never been a very good idea to call MessageBox() from an open event.

regards.

Hi, Ken -

Some ideas I would try if I were in your shoes:

1. Temporarily open a different window instead of wasset100 to see if execution returns to the SelectionChanged event script. Maybe something in wasset100 is now inadvertently causing the issue in 12.6.

2. When debugging the Open event in wasset100, does the execution call stack show execution came from the SelectionChanged event of tab_1 in w_main? What about when debugging same code in v12.1? Look for any differences.

3. Temporarily open the wasset100 window using the implicit global variable named wasset100 instead of the reference variable uo_1: Open(wasset100,Parent)

4. Temporarily try OpenWithParm and send a dummy parameter/object to wasset100 to try using a different "open" PowerScript command.

You realize, of course, that PB v12.6 is functionally obsolete and is no longer supported. Have you considered upgrading to Appeon PB? [no, I do not work for Appeon ;-) ]

HTH

Regards, John