The Image control is lightweight and supports scaling, tiling, and transparency.
Are you developing this for a , or for external commercial clients ?
4. The Distribution & Licensing Nightmare (Critical Warning)
: Unlike standard VB6 controls, FM20 controls handle Unicode strings. microsoft forms 20 object library vb6
' Example: Programmatically switching tabs MultiPage1.Value = 1 ' Switches to the second tab (zero-based) Use code with caution. Conclusion
If you are building a commercial application, it is highly recommended to use the standard Windows Common Controls or modern ActiveX components to avoid distribution limitations.
In VB6, this library allows developers to embed Office-style forms and controls directly into their applications without needing to use the full MSForms package from Office. The Image control is lightweight and supports scaling,
However, this library is the standard tool for creating reports in VB6. For reporting, you should use the built-in Data Report designer or the Data Environment . How to Create a Report in VB6 (The Standard Way)
Private Sub lstEmployees_Click() ' Display selected name MsgBox "You selected: " & lstEmployees.Column(1, lstEmployees.ListIndex) End Sub
It sounds like you're working with some classic VB6 (Visual Basic 6.0) and looking to use the Microsoft Forms 2.0 Object Library The Distribution & Licensing Nightmare (Critical Warning) :
A classic symptom of this unsupported usage is the notorious "Error 7 - Out of Memory" message. This error often appears when you build an application that uses this library and then deploy it to a user's machine that does not have Microsoft Office installed. The error stems from the fact that FM20.DLL has a dependency on components typically installed by Office, and without them, the library can fail or cause system instability.
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.
Companies like Sheridan, FarPoint, or ComponentOne provided robust VB6 compatible UI packs, though these are now also legacy. Conclusion
This library provides a specific set of controls that differ from the standard VB6 intrinsic controls. Commonly used objects include: Microsoft Learn MSForms.DataObject : Used for programmatic access to the system clipboard. MSForms.TextBox