|
|
|
Many programmers have developed custom controls using Visual Basic and then incorporated them into their C/C++ applications. Obviously, the C/C++ language has needed its own mechanism for creating custom controls. At the same time Microsoft was developing a solution, they
began
the migration from 16-bit Windows 3.1 to 32-bit Windows 95 and NT. As it turns out, the hardware-specific 16-bit VBX controls will not serve the new 32-bit multiple platform environments as well as programmers desired. Thus, Microsoft decided that rather than expand the VBX specifications, it would redesign the custom control architecture to include the 32-bit platforms; thus, the new control specifications with .OCX file extensions. Under Windows 95, 98, and Windows NT, OCX controls are the natural replacement for the older VBX custom controls of Visual Basic. These new custom controls will also serve container applications such as Microsoft Access, Excel, Word, PowerPoint, and so on. The
term
custom control has largely been
replaced
with ActiveX control.
|
|
|