MITCalc  Mechanical, Industrial and Technical Calculations

Your day-to-day partner on the way to an excellent product.   


English Czech German Chinese French Spanish Italian Portuguese Flags

Recommend to a friend

Home Page
CAD Support
Purchase, Price list
Contact us

OEM version

Useful links
News, Awards

Released MITCalc 1.72

Released MITCalc 1.70a
Released MITCalc 1.70
Extension Pack - EP08
Released MITCalc 1.61

Released MITCalc 1.60
Released MITCalc 1.51

Extension Pack - EP07
Service Pack - SP06

Released MITCalc 1.50

Released MITCalc 1.40b

Released MITCalc 1.40



Compatibility of calculations with various versions of Excel.

MITCalc supports a range of versions of Microsoft Excel. Although Microsoft claims that documents saved in various versions of Excel are mutually compatible, this is not entirely true and Excel 2010 irrecoverably damages documents saved in *.xls (*.xlsx, *.xlsm) format.

Luckily, this damage does not affect formulas and calculated values (the results of calculations are still correct !!!). However, inserted control elements in hidden areas (buttons, lists, select lists, graphs etc.) are moved and have their measures damaged when saved. These problems also occur in Excel 2007 to a lesser degree.

Luckily, this problem does not affect files saved in binary form (*.xlsb); such files have other additional advantages (smaller size, faster opening etc.). This is why we have prepared two installations. The first contains calculations in the *.xls format and is intended for Excel 2000/XP/2003 and 2007. The second installation contains calculations in the *.xlsb format and is intended for Excel 2007, 2010, 2013, 2016..... You should use the installation package which works for your version of Excel.

Note: For Excel 2007, you may use any of the installation packages. Before choosing, it is a good idea to consider whether you prefer compatibility for older versions or compatibility with newer versions of Excel.

The calculations can then be saved without the risk of being damaged as long as they are used on the same version of Excel.

Notes on the transferability of calculations between different versions of Excel.

If you are transferring calculations between different versions of Excel and wish to avoid problems with damaged control elements, save the calculation with all control elements visible. This means displaying the contents of all paragraphs on the "Calculation" list.

1) Transfer from Excel 2000, XP, 2003 to Excel 2007. Basically problem-free. You can also work with *.xls documents in Excel 2007, however *.xls files saved in Excel 2007 and opened in Excel 2000, XP, 2003 may contain deformed graphs.

2) Transfer from Excel 2000, XP, 2003, 2007 to Excel 2010. If you save an *.xls document in Excel 2010, 2013, 2016.... which has hidden areas with control elements, they will be damaged. We recommend either displaying all paragraphs on the "Calculation" list or saving the file directly in the *.xlsb format.

3) Transfer from Excel 2010, 2013, 2016.... 2007 to older versions. *.xlsb files are not directly readable in older versions of Excel. However Microsoft offers a so-called "Microsoft Office Compatibility Pack", which transfers *.xlsb files to *.xls files. Unfortunately, this conversion comes with the same problems mentioned above and control elements in hidden areas will also be destroyed. The only solution in this case is to open all the paragraphs on the "Calculation" list before saving the file in Excel 2010 (2007).


The table of file extensions used in the calculations is located below.

 File extension  Description
 *.xla  Excel add in (ver. 97, 2000, XP, 2003) contains macros in VBA
 *.xlam  Excel add in (ver. 2007, 2010, 2013, 2016...) contains macros in VBA
 *.xls  Standard Excel document (ver. 97, 2000, XP, 2003), may contain macros in VBA
 *.xlsx  Standard Excel document (ver. 2007, 2010, 2013, 2016...) does not contain macros in VBA
 *.xlsm  Standard Excel document (ver. 2007, 2010, 2013, 2016...) with support for VBA macros
 *.xlsb  Excel document (ver. 2007, 2010, 2013, 2016...) in binary form with support for VBA macros