Hi All

We have had a very weird issue for the last 3 weeks, since we moved our VDF 17.1 application to 18.0.

When a user has used the cWebBrowser object during the day, then at some time the DF application crashes. No DF error, just a windows dialog 'VisualLMS has stopped working'.
In the windows logs we found "faulting module ieframe.dll"

Click image for larger version.  Name: crash.png  Views: 145  Size: 24.8 KB  ID: 8189
We do use the a later IE version, by the setting
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULA TION]
"VisualLMS.exe"=dword:0000270f

The area I'm looking at right now, is the ActiveX properties. In the cWebbrowser object, the dialog is never shown, however settings are added to the source code.
We have a variety of settings across our cWebBrowser objects as well as the ie.vw from the samples;
Code:
             **     ** // These stars indicate the columns with the main difference of the below properties.
//Atradius
        TAAAAOZJAACJOAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAAAAAAAAAAAAAQAAAODQVwBzNc8RrmkIACsuEmIIAAAAAAAAAEwAAAABFAIAAAAAAMAAAAAAAABG
        gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA.
//Debtors
        TAAAAOZJAACJNQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAAAAAAAAAAAAAQAAAODQVwBzNc8RrmkIACsuEmIIAAAAAAAAAEwAAAABFAIAAAAAAMAAAAAAAABG
        gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA.
//Refreshed
        TAAAADJWAADOPQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAAAAAAAAAAAAAQAAAODQVwBzNc8RrmkIACsuEmIIAAAAAAAAAEwAAAABFAIAAAAAAMAAAAAAAABG
        gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA.
//Investigation report
        TAAAAGZZAAA5OwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAAAAAAAAAAAAAQAAAODQVwBzNc8RrmkIACsuEmIIAAAAAAAAAEwAAAABFAIAAAAAAMAAAAAAAABG
        gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA.
//DAW Sample ie view
        TAAAAP9MAACVKgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAAAAAAAAAAAAAQAAAODQVwBzNc8RrmkIACsuEmIMAAAAAAAAAEwAAAABFAIAAAAAAMAAAAAAAABG
        gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA.
//DAW Sample explanation
        TAAAAFFEAAAHLAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAAAAAAAAAAAAAQAAAODQVwBzNc8RrmkIACsuEmIIAAAAAAAAAEwAAAABFAIAAAAAAMAAAAAAAABG
        gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA.
//DAW XML View
        TAAAAOA8AACOIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAAAAAAAAAAAAAQAAAODQVwBzNc8RrmkIACsuEmIIAAAAAAAAAEwAAAABFAIAAAAAAMAAAAAAAABG
        gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA.
I am despirate to find out what these properties are and if they are needed at all...
So I fired up MS Visual Studio to start a Windows forms project with a cWebBrowser, to see if the ActiveX properties are shown there. They are not... And there are no 'defaults' therefore either.

Should I just remove this section in the DF code, never press ActiveX properties for the webbrowser and it should work?

Any comments are very much appreciated!

Cheers
Marco