Technically, the library is an ActiveX component (FM20.DLL). In VB6, while the default controls are intrinsic to the runtime (msvbvm60.dll), the Microsoft Forms 2.0 controls are external ActiveX objects. This distinction is subtle but vital. It meant that while standard VB6 controls were tightly coupled with the language runtime, Forms 2.0 controls were "in-process" servers that could be shared across the Microsoft Office suite. This architecture allowed for a unified look and feel between custom dialog boxes in Excel and standalone applications created in VB6, a significant advantage for enterprise developers building integrated office solutions.
Before you start building, there are critical legal and technical "gotchas" to keep in mind: Collections, controls, and objects (Microsoft Forms) microsoft forms 20 object library vb6
FM20 controls sometimes struggle with the VB6 Tab order and focus management. You may find that the GotFocus and LostFocus events behave slightly differently than their intrinsic counterparts. Container Requirements Technically, the library is an ActiveX component (FM20
The Forms 2.0 library is not just about controls. It includes supporting objects like: It meant that while standard VB6 controls were