Skip to main content
SteveMackey1-Visitor
1-Visitor
Nov 23, 2010 5:45 PM UTC
Question

ComboBox VBScript error

I have recently updated my computer to a 64 bit Windows 7 platform. I am now getting an error while using MathCad 14.0 M020 on spread sheets that have worked previously using combo boxes. The error is "Microsoft VBScript runtime error Line16 Error0 Object required: 'ComboBox'". And when I try to insert a Component-Scriptable Object, the Microsoft Forms* selections are not even available as on option. During the initial install of MathCad 14 the .NET Framework prerequisites were not installed from the CD. I have manually installed the .NET Framework 3.5 and the Microsoft Report Viewer which includes the Microsoft Forms. I also upgraded my MSXML 4.0 SP2 to MSXML SP3. I then uninstalled and reinstalled MathCad 14 and am still getting the same error. Has anyone came across this before?

22 replies

MikeArmstrong1-Visitor
1-Visitor
Nov 23, 2010 8:29 PM UTC

I haven't come across this before, but you try contacting the Mathcad License and Install team directly.

-.

Mike

Translate
ptc-41636431-Visitor
1-Visitor
Nov 29, 2011 11:00 AM UTC

Hi Steve,

Im also encountering your problem, have you figured out the cause? Before i can also run the combo box but when i used windows 7 and mathcad15, its not working anymore. Thanks

Translate
MikeArmstrong1-Visitor
1-Visitor
Nov 29, 2011 12:42 PM UTC

What version of M15 have you got?

Mike

Translate
ptc-41636431-Visitor
1-Visitor
Nov 30, 2011 12:54 AM UTC

Hi Mike,

How to know the version of mathcad im using? Is It this? Mathcad 15.0 (M010 [MC15_M010_20110622])?

When i try to insert a combo box, i can place it on the worksheet but i cannot edit its script because when i right

click on it it says internal error

Thank you

Translate
RichardJ19-Tanzanite
19-Tanzanite
Nov 29, 2011 3:05 PM UTC

There seems to be two threads going on this subject:Object required:'Combobox1'

It looks to me as though the MSForms 2.0 controls, including the Conbobox, and not compatible with the 64 bit OS.

Translate
ptc-41636431-Visitor
1-Visitor
Nov 30, 2011 12:58 AM UTC

I think so too because i've tried with different laptops all with the same OS, windows7 64 bit still the error occurs. Do you have idea on how to fix it? Thank you very much

Translate
RichardJ19-Tanzanite
19-Tanzanite
Nov 30, 2011 2:41 PM UTC

Do you have idea on how to fix it?\

No, sorry. I'm still using XP.

Translate
Ramakr561-Visitor
1-Visitor
Sep 17, 2019 9:42 PM UTC

Just Change your MS office from 64bit to 32bitversion ( mathCad 15 is a 32bit application)

 

Ramak

Translate
tlpeng-itdept5-Regular Member
5-Regular Member
Aug 21, 2024 8:40 AM UTC

We experienced this error after reverting back to Win10 from an accidental upgrade to Win11. I have seen some indication that 32bit VBA has been deprecated in Win11. Assuming that, Msoft in its great wisdom, did not feel it necessary to restore the removed 32bit VBA components when reverting back. Indeed, there was a message when reverting back that some apps would fail to work correctly.

 

The missing component is the 32bit version of "Microsoft Forms 2.0 Object Library" made up of 2 files: fm20.dll and fm20ENU.dll in \SysWOW64 (the 32bit system area - note that those same files in \System32 are the 64bit versions on 64bit Windows, which Mathcad15 cannot access, being a 32bit app). What proved to be quite difficult was how to reinstall the Library. There does not seem to be a download/installer for the Library. I was not able to determine how the Library was installed in Win10 originally. While 32bit Office definitely installs it, 32bit Office had never been on this PC - only 64bit Office. I'm not sure if Win10 came with it originally, or if some other 32bit app on the PC installed it. BTW, this is a strong indicator that Mathcad15 will not run on Win11 without some kind of manual intervention.

 

SOLUTION:

Find fm20.dll and fm20ENU.dll in the \SysWOW64 of another PC and copy them over to the same folder of the broken PC. Be sure to not mistakenly take the ones in the \System32 folder. Then register those 2 files by opening an Admin command prompt in the \SysWOW64 directory on the broken PC using the 32bit regsvr32 command (not the 64bit regserver command). Simply enter >regsvr32 fm20.dll, etc. NOTE: I would strongly caution against downloading these .dll's from 3rd party websites, as some sites suggest. Much safer to get them from one of your own, known trustworthy PCs.

 

Trivia: Ever wonder what the WOW means in \SysWOW64? Windows-On-Windows, meaning 32bit Windows running on top of 64bit Windows.

Translate
    DD_1391035510-Marble
    10-Marble
    Jul 28, 2025 1:07 AM UTC
    @tlpeng-itdept wrote:

     

    SOLUTION:

    Find fm20.dll and fm20ENU.dll in the \SysWOW64 of another PC and copy them over to the same folder of the broken PC. Be sure to not mistakenly take the ones in the \System32 folder. Then register those 2 files by opening an Admin command prompt in the \SysWOW64 directory on the broken PC using the 32bit regsvr32 command (not the 64bit regserver command). Simply enter >regsvr32 fm20.dll, etc. NOTE: I would strongly caution against downloading these .dll's from 3rd party websites, as some sites suggest. Much safer to get them from one of your own, known trustworthy PCs.

    The actions you have indicated are sufficient to perform only with the fm20.dll file, in addition, performing registration for the second file causes an error.

    Translate
    Terms & ConditionsAccessibility statement