I have a form with an ActiveX Control (Shell Explorer). With this, I am showing HTM documents with .Document.DesignMode="on". We discovered on multiple installations (every single one that we have tested), that the 3 and the 9 keys on the number pad don't type anything in. All other numbers, symbols, and enter key all work. Of course, this is with number lock on. On my keyboard, if I take number lock off, the 3 is the Page Down and the 9 is the Page Up. These do work.

In case you need it, I'm running Windows 10 with IE 11.535.18362.0, but previously tested on 11.1066.14393.0 (though I believe Shell Execute is stuck in IE7 (see https://weblog.west-wind.com/posts/2011/may/21/web-browser-control-specifying-the-ie-version and I did try putting in the meta tag to use the latest)).

Does anybody have any ideas for me? I appreciate your help!!

Thanks, Matthew

Just double checked this in Help Builder and I have no problem using the NumPad 3 and 9 keys in the Editor there (HTML editor control).

What are you doing inside of the control? Is it possible there are keyboard events firing that prevent those keys from getting typed through.

You almost certainly will want to use IE11 mode and not stick with native IE7 mode because the old browser functionality sucks for rendering, perf and just about everything else. The Edge header is all you should need, but for more reliable behavior with dependencies and all documents loaded the registry hack is the best solution. Make sure you set it both for vfp.exe as well as your executable (as part of a setup program or during first app startup).

+++ Rick ---