HomeTechniques and TipsVBA Programming with @RISK@RISK 5.x VBA Macro Compatibility with 6.x/7.x

10.15. @RISK 5.x VBA Macro Compatibility with 6.x/7.x

Applies to: @RISK for Excel 5.x, upgrading to @RISK 6.x/7.x Professional or Industrial Edition.
(@RISK Standard does not support automation.)
For compatibility of other releases, see Upgrading Palisade Software.

I wrote some macros that call @RISK functions listed in the Developer Kit documentation in @RISK 5.x. Will they work in @RISK 6.x/7.x?

@RISK 5.x macros will work in @RISK 6.x/7.x, with the exception mentioned below, but you will need to update the reference in Visual Basic Editor » Tools » References.

You need to update the reference when transitioning to @RISK 6 or @RISK 7, but not when transitioning between two @RISK 6.x version numbers or between two 7.x version numbers.

If you have a workbook with @RISK 5 automation code, follow this procedure to convert it to @RISK 6.x/7.x:

  1. Launch @RISK and open your workbook.

  2. Press Alt-F11 to launch Visual Basic Editor.

  3. Please see Setting References in Visual Basic for the appropriate references and how to set them.

  4. If you have 64-bit Excel, macro code in @RISK 5.7 required some special code beginning with #If Win64 Then. That code is no longer necessary in @RISK 6.x/7.x, so remove it.

  5. Click OK, close Visual Basic Editor, and save your workbook.

Repeat these steps for each workbook where your VBA code calls RISK functions.

Exception: Some macros from @RISK 4.5 were implemented in @RISK 5.0.1 through 5.7.1 as "wrappers" for 4.5 macros. Those wrappers no longer exist in @RISK 6.x/7.x because they were incompatible with Excel 2010. If you have working @RISK 5.x macro code that fails in @RISK 6.x/7.x, even after setting the correct references, the problem is probably those legacy 4.5 features that are no longer supported.

Additional keywords: XDK

last edited: 2015-06-18

This page was: Helpful | Not Helpful