Hint for users who also experience a strange behaviour of iGrid 4.70 when using ResizeXtra-RXSplitter:
When you drop a grid into a container of a RXSplitter-control, the grid will not be resized correctly when resizing the form.
To solve this problem I deleted the iGrid 4.70 out of the container, puted in an iGrid 4.60, then deleted this grid again and droped in a new iGrid 4.70 again. I've tested this several times with new projects and this is the only way I know to use the new version of iGrid properly with the ResizeXtra Splitter-control.
:) hope this is helpful for you...
Thommy

Just one comment from the iGrid developer's side.

There are many "universal" splitter/control resizing components, but many of them use some Windows API tricks or non-standard native window messages processing and because of that we may see incompatibility with other products.

We recommend that you test our iGrid and other ActiveX's thoroughly with such components before you make the final decision to use them in real-world apps.

Hi Igor
Which of these splitter/resizing - components would you recommend for a VB6 app? Do you have a favourite, or do you do such resize-action by code?

We are always coding resizing, i.e. do it "by hands" in VB code. Though it may look tedious, it never failed.

Never used any external resizing component. Maybe, intuitively feeling that it may have potential problems described above :)

So we recommend to code resizing "manually", and this concerns not only our iGrid but any ActiveX control.

I really do understand what you mean 😉 so I'll try doing most of my resizing with coding. Thanks for your advise 🙂

We also write our own resizing code just because we haven't found anything that's trouble-free and efficient, and to cut down on the number of DLL/OCX dependencies. We also like the control we have by doing it ourselves.

You may also want to contact Evova and send them a demonstration project showing the issue. It's possible there's a bug in their software no one else has reported to them.