All I got was there were some cases raised regarding ActiveX issues and office. Told to wait a couple of weeks and check later builds to see if it is fixed!

Seems MS support can't raise an issue with the development team.

I created a simple Excel workbook with my form and the IGrid control. Build 9001.2138 it is fine, later builds it is not. Thought they might be interested if it was simple to reproduce.

Just tried Build 1806 10211.20004, still not fixed

I managed to find another work around that may also shed light on the issue.


In the status bar of Microsoft Word there is a Display Settings option.

Apparently option only shows in status bar if it detects there’s a possibility for rendering issues:

Note: The status bar will show a “Display Settings” indicator that appears whenever the app is in “Optimize for compatibility” mode, or whenever the app detects there’s a possibility for rendering issues. You can click that to quickly change between modes (app restart still required).

Setting this option to Optimize for compatibility fixes the issue and the control works as expected again.

The setting is also located in Word Options on the General tab under User Interface Options.

The label reads When using multiple displays: (both my test machines are using multiple displays but I haven't confirmed with clients if they are using multiple displays... maybe why not everyone can reproduce).


Office support for high definition displays:
https://support.office.c...S&rs=en-US&ad=US 

While still not a fix... it's easier for clients to change setting than roll back office and may help narrow down the issue.

This fixes the issue even if there is only a single monitor. My customer has a single monitor, my consultant with the issue is a single monitor but sometimes connected to another monitor. My test machine is a VM with a single monitor. Given it is set to optimize for best apperance and setting it to optimize for compatability fixes it, I wonder what it is doing as my application has some iGrids that work and others that don't.

Just tried the June 1 Build 1806 10228.20021 update, still not fixed
Just tried the June 8 Build 1807 10301.20006 update, still not fixed

Hi All,

I have the same issue here. On a Multipage tab the iGrid is not visible when starting Word. When I run the form and do some actions and then close the form (hide) I go the the VBA Editor and click on the stop button in VBS. In Dutch it is called [Beginwaarden]. Then I start the form again and the iGrid is visible. STrange behaviour but when I close Microsoft Word and start it again I get the same issue and after the start of the form, doing some actions and hide the form and stop the code it works again. So Consistent behavior in my case but nothing that helps me find a solution for using it for my end-users. The fix devwave called in the Word options did the trick (thanx man).

Now we set the following registry key to make it work:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options]
"RenderForMonitorDpi"=dword:00000000


So where is the issue? In Microsoft Office or in the ocx? I don't know but the most important question is who can fix it permanently?

iGrid had worked in Microsoft Office flawlessly for years. This problem appeared only in one of the recent builds of Office this year, when Microsoft "enhanced" their Office suite to support high-DPI monitors better. As we understand the nature of the problem, Microsoft is trying to block OCX controls if they think the controls may not work properly on high DPI screens. It looks like an issue on their side, not in iGrid. At least, at the moment we do not know how to tell Word or Excel that our control must not be blocked in this scenario.

I have found other mentions of this issue:

https://www.add-in-expre....php?FID=5&TID=15006 

http://kb.palisade.com/i....friendly&id=5#p1706 

It turns out that the "Optimize for best appearance" feature affects not only ActiveX's but even other native Microsoft technologies like Windows Forms .NET.

Interesting, has something changed in the latest builds of Microsoft Office and they already fixed this problem? If you experienced this issue with iGrid ActiveX in Microsoft Office earlier, can you write some lines and tell us how things are now.

I've just done an update to the latest Build 1901(11220.200008) and the issue appears to have been resolved.

I've just done an update to the latest Build 1901(11220.200008) and the issue appears to have been resolved.

Don't have access to the version yet as a regular 365 subscriber. Looks like it went out to some office insiders and Microsoft Office 365 ProPlus users only so far.

No mention on 365 update page as of yet:
https://support.office.c...a-42c1-914f-bca4603e1426 

So much for the the 365 description LOL:

Office 365 is a subscription service that ensures you always have the most up-to-date modern productivity tools from Microsoft.

Microsoft Office 365 Business

Jan 04, 2019 Updated from 1811 to 1812 (11126.20188)

Still broken after 9 months.

Confirming again that it's never safe to update a Microsoft product. The tiny changes Microsoft Office makes to improve the software usually involves moving the same feature to another location so the user cannot find it! Having the most up to date version, which we obviously don't have anyway certainly doesn't seem worth the trouble, just so they can call it an update. They should concentrate on just updating the bugs.

Highly doubt any of our clients are getting updated to version 1901 either.

Version 1901 (build 11231.20130)
Version 1901 (build 11231.20174)

Neither of the latest versions of 1901 fix the issue.

Control still fails to load unless switched to optimize for compatibility.

All my igrids are no longer displayed. I can see them (gray frame when clicking), but they are not visible.

I am using Office 365 16.0.11901.20070 32 - bit. What do I have to do to make the igrigs visible again?

Juwelix, have you tried to set the Optimize for compatibility option in the Word/Excel settings as it is described above?