iGrid is fully compatible with all 32-bit and 64-bit releases of Microsoft Windows. It was tested and works well both in all client and server editions of Windows (Windows 95/98/Me/NT4/2000/XP/Vista/7/8/10 and Windows Server NT/2000/2003/2008/2012/2016 respectively).
iGrid is being developed in Microsoft Visual Basic 6. Despite this fact, native Windows API calls and COM interfaces are widely used inside iGrid to get the maximum performance and provide the best experience on the Windows platform.
The iGrid ideology is to support the look and feel of the OS. For instance, by default all constituent parts are automatically drawn using visual styles in systems like Windows 7 or Windows 10 (this feature can be optionally disabled using the corresponding iGrid properties).
To use iGrid in your end-user application, you just need the VB6 run-time support library (MSVBVM60.DLL) installed in your system. All modern versions of Microsoft Windows are supplied with this library or this library is installed as a part of all latest releases of Microsoft Office. As a result, iGrid can be used on all modern systems without installing additional libraries. In any case you can always get the redistributable package of the VB6 run-time library from Microsoft's Downloads site or from this one for free and install it if required.
32-bit and 64-bit applications
iGrid is compiled in VB6 that produces only 32-bit executable code. Because of this, iGrid can be used 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 is compiled in VB6 as a full-featured ActiveX control and in theory it can be used in any development environment that supports ActiveX controls - not only VB6 itself or Microsoft Office VBA. However, not all development environment support all features of the ActiveX standard and we recommend that you test iGrid thoroughly in your development environment that differs from VB6/VBA before buying the product.
Below you will find some notes regarding well-known non-VB6 development environments.
Microsoft Office VBA 97/2000/XP/2003/2007/2010/2013/2016
iGrid works well both in Microsoft Word/Excel UserFroms and on Microsoft Access forms, and its members can be easily accessed from VBA code. The only exclusion is the
ScrollBarThicknessChanged event used very rarely only if you are developing an application that should react on the changes of the scroll bar thickness. This iGrid event does not work in Microsoft Office VBA due to some Windows API restrictions in UserForms.
As written above, iGrid does not work in the 64-bit versions of Microsoft Office. With the release of the 64-bit version of Microsoft Office 2010, Microsoft abandoned the whole world of legacy 32-bit COM ActiveX components. The Office developers write 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 that cannot produce 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 Microsoft Office for iGrid ActiveX, though 32-bit Office solutions with iGrid can be used in 64-bit editions of Microsoft Windows without any problems.
Microsoft Visual C++ 5.0-11.0
iGrid can be used in Microsoft 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 is totally based on the COM technology.
Microsoft 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 Microsoft 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. Obviously, this problem was fixed in the two latest versions of VFP because the same iGrid ActiveX works well in VFP 8 and 9 without any changes.
Borland Delphi 2.0-7.0, 2007-2012
A couple of our testers tried to use our grid on Delphi forms, but they had the same problems like in Microsoft 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.