iGrid is fully compatible with all 32-bit and 64-bit releases of the Microsoft Windows OS. It was tested and works well both in the client editions of Windows (95/98/Me/NT4/2000/XP/Vista/Windows 7 and Windows 8) and the server editions (NT/2000/2003/2008/2012).
iGrid is being developed in MS Visual Basic 6, but despite this fact it widely uses native Windows API and COM calls to get the maximum performance on the Windows platform.
The iGrid ideology is to support the look and feel of the OS it is working in to the max. For instance, all the constituent parts are automatically drawn using visual styles in such systems as Windows XP, 2003 or Vista when visual styles are turned on in the OS (this can be optionally prohibited using the iGrid properties).
To use iGrid in your end-user application, you just need the VB6 run-time support library installed in your system (the main file is MSVBVM60.DLL). This is not a problem for almost all versions of MS Windows as they are supplied with this library (that's true for such versions as Windows XP, Vista or Windows 7), or this library comes with all latest releases of MS Office. In any case you can always get the redistributable package of VB6 run-time library from Microsoft's Downloads site or from this one for free.
32-bit and 64-bit applications
iGrid is compiled in VB6 and it is a 32-bit executable code. Because of this, it can be compiled as a part of only 32-bit exe applications - though they can work well in a 64-bit environment.
Using iGrid in non-VB6 development environments
iGrid OCX is compiled with VB6 IDE as a full-featured ActiveX control, and in theory can be used in any development environment that supports ActiveX controls. However, you should test iGrid OCX thoroughly in your non-VB6 environment before you buy it because some environments can use ActiveX in its own way (like MS Visual FoxPro).
Below are some notes regarding well-known non-VB-based development environments.
MS Office VBA 97/2000/XP/2003/2007/2010/2013/2016
iGrid OCX works well both in MS Word/Excel UserFroms and on MS Access forms, and can be easily used in VBA code. The only exclusion is the almost unused
ScrollBarThicknessChanged event which does not work due to some API restrictions in UserForms (it is used only if you are not developing an application that should react on the changes of the scroll bar thickness).
As written above, iGrid does not work in the 64-bit versions of MS Office. With the release of the 64-bit version of MS Office 2010, Microsoft abandoned the whole world of legacy 32-bit COM ActiveX components. They say that "Existing 32-bit ActiveX controls, both third-party and Microsoft-supplied, are not compatible with the 64-bit version of Office 2010." (more info can be found in this MSDN article in the section "ActiveX Control and COM Add-in Compatibility".
iGrid ActiveX is built using Visual Basic 6 which does not allow to build 64-bit code, and because of this we will never see the 64-bit iGrid ActiveX. This means that you need to use only the 32-bit versions of MS Office for iGrid ActiveX.
MS Visual C++ 5.0-11.0
iGrid can be used in MS VC++ like any other ActiveX control. Just take into account the fact that you need to write a little bit more code to access the iGrid members than in Visual Basic as iGrid are totally a COM technology based control.
MS Visual FoxPro 5.0-7.0, 8.0 and 9.0
The iGrid control can be used in the forms of the two latest versions of MS Visual FoxPro - 8.0 and 9.0. However, we recommend that you test the control thoroughly in VFP before you buy it as iGrid had some problems with the scroll bars drawing in the earlier versions 5.0-7.0. Most likely, it was an internal error in VFP that did not allow us to use the standard Win32 API scroll bars in iGrid, and it was fixed in the latest versions of VFP because the same control works in them without any changes from our side.
Delphi 2.0-7.0, 2007-2012
A couple of our testers tried to use our grid in Delphi forms, but they had the same problems as in MS VC++. To use an ActiveX control in Delphi, you need to deal with its type library and transform VB syntax using the COM control interface. Moreover, COM data types (such as Variant) are not native to Delphi, and you will get additional problems with them if you want to use iGrid in Delphi. Delphi programmers also say that VB is the ideal development environment for iGrid.