2 Replies Latest reply on Mar 30, 2018 2:26 PM by rschmitz

    mshflexgrid on processbook display



      I want to use mshflexgird on a PB display in order to show data.The control shows up as blue box with a heading at the top containing the name of the control. The object does not have properties.

      is there any way to fix the problem or replacement


        • Re: mshflexgrid on processbook display

          Hi Xing,


          Any time there's a blue box like this, it means that ProcessBook is not able to successfully render the ActiveX control that's supposed to be there.


          In this case, the ActiveX control is the Microsoft Hierarchical FlexGrid Control, which is handled via C:\Windows\SysWOW64\mshflxgd.ocx (note: msflxgrd.ocx is a different file handling a different flex grid ActiveX object, so make sure you are looking at the right one).


          What I would like to try next for troubleshooting:

          1. Do you have this file in the correct location? If not, then you will need to obtain this file before proceeding. It's a Microsoft file so obtaining it from another machine on your network, a Microsoft download page, or even a reinstall of Windows (although that's very drastic) would be the best options.


          If you have the file, then continue on to the next step:

          2. When you make a new ProcessBook display, can you add a control and see if you have the Microsoft Hierarchical FlexGrid Control option:

          2. a. If it is there, can you add it to the display and see if it works?

          2. b. If it's not there, can you attempt to manually register it?

          Open a command prompt as admin and run the following command:

          regsvr32 "C:\Windows\SysWOW64\mshflxgd.ocx"


          3. Another thing you could try would be to delete any cached exd files in the %temp%\PB<versionnumber> directory (for example: "C:\Users\kduffy\AppData\Local\Temp\PB361"). Exd files are cached forms of ActiveX controls; it helps in terms of performance to load from these files rather than the ocx main file, but if these cached files become corrupted they can be very problematic. When troubleshooting, it's best to get rid of them.