Any language that supports calling ActiveX components (also known as OLE Automation servers), should be able to make calls to IOM interfaces. This includes virtually every programming language product available on the Windows platform.

Microsoft designed the ActiveX components technology with a heavy bias towards meeting the needs of Visual Basic. In fact, much of the technology is effectively a part of the Visual Basic run-time environment. Furthermore, in its own implementations of ActiveX components (such as in the Microsoft Office Suite), Microsoft has documented the interfaces in terms of the Visual Basic language.

Based on this convention and on the wide use of Visual Basic as a Windows programming language, we have also decided to document the SAS IOM interfaces in terms of Visual Basic language syntax and conventions. Programmers in other languages have already become accustomed to interpreting such documentation and translating it to their native conventions. Visual C++ programmers are one common group that must do this. This document includes an additional section to help this group with that task.

The .NET runtime, with its family of languages including C# and VB.NET, represents the latest direction in Windows programming. ASP.NET is now the environment of choice for Windows web applications. The .NET environment also supports traditional desktop GUI clients similar to those that were developed with Visual Basic forms in VB6. IOM integrates fully with .NET through the use of COM Interoperability. For more information, see Programming in the .NET Environment.