Add-in and Excel 2007

Question

Hi everyone,<BR><BR>Does anybody know if essbase Add-in version 6.5.5 will work togehter with Excel 2007? I really cannot find any detail on this.<BR><BR>Thanks in advance<BR>

Answer 1

Chances are, your VBA code isn't broken because of the API, but because the old xls/xla workbook had a reference to the old excel object model.<BR><BR>Go to the VBA editor and choose the Tools/References menu item. Look for any "missing" entries and perhaps the new version of excel has an equivalent. If a reference is missing, it can cause certain functions to lose their definition and it shows up as broken code (i.e. no definitions for string functions like len, format$, etc... is a frequent side effect).<BR><BR>There is another possibility, a more pervasive and complicated one (at least to explain). Excel 2007 may be interpreting the module defines differently. The API modules with essbase use a patter like this:<BR><BR>1: Declare Function EssSomething1 Lib "esbapin.DLL" (etc...)<BR>2: Declare Function EssSomething2 Lib "esbapin" (etc...)<BR>3: Declare Function EssOtlSomething1 Lib "esbotln.DLL" (etc...)<BR>4: Declare Function EssOtlSomething2 Lib "esbotln" (etc...)<BR><BR>The first definition sort of "keys" the dll to the VBA module, so subsequent references don't particularly need the .DLL extension. The problem is that if the first use of the dll doesn't include the extension, the dynamic linking isn't always resolved properly. In at least one case, I've had to add the extension TO EVERY SINGLE DECLARE. This resolved my issue, and it wasn't especially difficult to do, but I have no definitive explanation for why it was necessary or what made to resolve the issue.<BR><BR>So, do I recommend you try this fix? Only as a last resort. I'd check the references for missing modules first, as it's more likely to be an issue and it's really easy to do.<BR><BR>HTH,<BR><BR>-Doug.<BR>