Hi Balu,

I have also had issues with the IE Control running Javascript.  It can be intermittent following updates, etc.

There is a registry setting to control whether the Browser can run Javascript.  Using the normal IE browser you would normally get prompted or a warning, but this is not the case with the activex control.

Computer\HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_LOCALMACHINE_LOCKDOWN

Set the value for iexplore.exe to 0.  I use the following code in my window to check and set the value.

//Set Registry Value to allow IE object to run Active Scripts, including javascript
Integer li_result

ulong lul_num, lul_set

li_result = RegistryGet("HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_LOCALMACHINE_LOCKDOWN", "iexplore.exe", RegULong!, lul_num)

if li_result = 1 and lul_num <> 0 then

lul_set = 0

li_result = RegistrySet( "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_LOCALMACHINE_LOCKDOWN", "iexplore.exe", RegULong!, lul_set)

if li_result = -1 then MessageBox('Error Setting Registry Value!','Error setting Active Scripts Registry Value.')

end if

I hope that helps.

Michael

We tried clearing the cache and that didnt seem to fix the issue either.

Any help on why the MS Web Browser control would freeze while trying to execute a javascript would be helpful. Thanks!

Try using my WebBrowser wrapper object and see if it makes any difference.

http://www.topwizprogramming.com/freecode_webbrowser.html

running in PB desktop, can work but not work after compile with appeon

@here,

A quick update. We were able to pinpoint the issue  to google analytics and the team responsible for it made some changes in the sequence and that seems to have taken care of this. I really appreciate your time and all the ideas. Thank you!

On a different note, After upgrading our code base to 2017 R3, we had numerous crashes relating to the OLE browser control. It appears the OLE control hasn't been instantiated when the window open event makes a navigate call to the ole control resulting in an Error 35. We moved that code to pfc_postopen and check the validity of the ole control now before we make a navigate call the ole control. This seems to have fixed this issue.

This behavior was NOT observed in the previous versions of Powerbuilder. Not sure if anything to do with the event sequence or to do with the OLE browser got changed in 2017 +