MATLAB: Am I unable to use the Excel Add-in created using MATLAB Builder for Excel 1.2.9 (R2007b) after installing MATLAB 7.8 (R2009a)

MATLAB Builder EX

I am using a MATLAB built add-in and also the Spreadsheet Link EX simultaneously in a macro-enabled Excel workbook. The add-in was generated using MATLAB Builder for Excel 1.2.9 (R2009a). I intend to use both the Spreadsheet Link EX 3.0.3 (R2009a) and the add-in (which corresponds to R2007b) in my Excel workbook through a VBA macro.

To my horror, when I tried using the add-in after installing the newer version of MATLAB, none of the data values were updated in my Excel sheet, which indicated that the call to the add-in did not work.

I have tried all the usual tricks such as rearranging the MATLAB/ MATLAB Compiler Runtime directories in the system path, registering the older version of MATLAB as COM automation server, etc. I am unable to use the add-in even when I do not interface with the Spreadsheet Link EX in my VBA macro.

There are no error messages.

Best Answer

Check the version of MWComUtil type-library that is referenced by the VBA macro. There is a possiblility that after installing the newer version of MATLAB, the newer version of MWComUtil is being referenced and thus is incompatible with the add-in which was created against the older version of the DLL.

You may need to re-register the older version of MWComUtil, the one that corresponds to R2007b, in the DOS shell as follows:

 mwregsvr mwcomutil.dll

Related Solutions

MATLAB: I have two versions of MATLAB installed on the computer, why am I unable to use MATLAB Builder EX with one version and not the other

This automation error is caused due to the system environment variable setting for the PATH variable.

When a file or collection of files is compiled in MATLAB using 'deploytool', the version of MATLAB that you are compiling the application on must be before all other versions of MATLAB in the system path. Otherwise, the application will try to look for the wrong libraries when it is running the deployed application and this may result in errors.

Specifically, this error was caused because an incorrect version of mbuild was being used during compilation. This causes the Builder EX generated COM dll to link against a different mclmcrrt7x.dll. Installing MATLAB 7.8 (R2009a) adds $MATLABROOT9a/bin on the path ahead of the MATLAB 7.6 (R2008a) path and since mbuild.bat resides in $MATLABROOT/bin folder, the MATLAB 7.8 (R2009a) mbuild is called by mcc.

To workaround this issue, please enter the following command at the MATLAB command prompt:

setenv('PATH',(matlabroot) '\bin;' getenv('PATH'))

Verify that this worked by using the following command:

getenv('PATH')

You should see $MATLABROOT_8a/bin first on the path.

Some important caveats to note:

1.) You must exit out of ALL Microsoft applications before the path updates will take effect. This includes Microsoft Outlook, Word, Power Point, Excel, etc.

2.) You must restart MATLAB and recompile your application after this is done. Double check that your path settings are correct by typing "getenv('path')" at the MATLAB command prompt in order to ensure that the path is in the correct order.

Please refer to the Related Solution below to check how to change your System PATH.

MATLAB: How to use two different versions of MATLAB Compiler Runtime with VBA code for MATLAB Builder for Excel

It is not possible to use add-ins that were compiled with different versions of MATLAB Builder for Excel from within the same application; however they can be accessed from separate applications.

In order for your add-ins to be accessed from separate applications, you will need to make sure that both versions of MATLAB or MATLAB Compiler Runtime (MCR) are on the path, and that both the components have been registered on the machine (via regsvr32/mwregsvr).

You must also register mwcomutil.dll and mwcommgr.dll for each version of MATLAB or MCR you are using. To learn more about registering components, refer to the following documentation:

https://www.mathworks.com/help/compiler_sdk/com/registering-and-referencing-the-utility-library.html

In the VBA code, you can invoke the version-specific mwcomutil.dll by using the syntax

             Set MCLUtil = CreateObject("MWComUtil.MWUtil7.4") ' To use version 7.4

or the version-independent DLL using

             Set MCLUtil = CreateObject("MWComUtil.MWUtil") '<---can end MWUtil with 7.4 or 7.2 or appropriate version

Best Answer

Related Solutions

MATLAB: I have two versions of MATLAB installed on the computer, why am I unable to use MATLAB Builder EX with one version and not the other

MATLAB: How to use two different versions of MATLAB Compiler Runtime with VBA code for MATLAB Builder for Excel

Related Question