The Microsoft Forms 2.0 Object Library is a type library associated with the dynamic-link library file . It provides a collection of controls and objects primarily designed for use within Microsoft Office's Visual Basic for Applications (VBA) environment, such as the forms you see in Excel, Word, or Access. However, because VB6 shares a common heritage with VBA, it is also possible to reference and use this library within a VB6 project.
If your app strictly requires Unicode, use third-party ActiveX controls designed for VB6, or consider migrating the UI logic to a modern framework like .NET's WinForms.
While VB6 has an Image control, the FM20 version handles transparency and various image formats more gracefully within the Form container. Important Deployment Warnings microsoft forms 20 object library vb6
: Your users must have a licensed copy of Microsoft Office. FM20.dll is not redistributable without an Office license. If your app runs on a server (e.g., a Windows Service), you cannot rely on this library.
(Note: When populating FM20 controls in pure VB6, you can also use the .AddItem method and assign values to specific cells using the .List(row, column) property matrix). The Critical Caveat: Licensing and Redistribution Issues The Microsoft Forms 2
: Unlike MSCOMCTL.OCX, you cannot legally copy FM20.dll to C:\Windows\SysWOW64 on a machine without Office and expect it to work. It will fail or violate licensing.
The file is usually located in the C:\Windows\System32 folder on 32-bit systems or the C:\Windows\SysWOW64 folder on 64-bit systems, though it may also reside within the Microsoft Office installation directory. If your app strictly requires Unicode, use third-party
These controls are designed for VBA, not VB6. You may encounter issues with focus handling, events, and performance.
If you need a modern look and feel without the redistribution issues of FM20.DLL , consider these alternatives: