basic examples only work with a modification of xlpython.xlam

[alex-ifx]

Hi!

I have just started with xlpython today and I was unable to run this example:

from xlpython import *

@xlfunc
def DoubleSum(x, y):
    '''Returns twice the sum of the two arguments'''
    return 2 * (x + y)

Excel was complaining about the following line:

Sub XLPMacroOptions2010(macroName As String, desc, argdescs() As String)
    Application.MacroOptions macroName, Description:=desc, ArgumentDescriptions:=argdescs
End Sub

I have changed it to:

Sub XLPMacroOptions2010(macroName As String, desc, argdescs() As String)
    Application.MacroOptions macroName, Description:=desc
End Sub

... and now it works.

What is causing this and how can I avoid this situation?

I use Windows 7 and Excel 2007.

Thank you!

Best regards,
Alex

[ericremoreynolds]

Hi Alex,
The line

Application.MacroOptions macroName, Description:=desc, ArgumentDescriptions:=argdescs

is indeed invalid on Excel 2007, but the VBA code should be written in such a way that it does not enter into that function on versions < 2010, so I do not understand why it is raising this error. (I myself use 2007 and it doesn't complain.)

Could you do me a favour and tell me what the output of typing

?Application.Version

is on your PC?

Thanks, regards,

Eric

[alex-ifx]

It is 12.0

[ericremoreynolds]

It not clear to me why the line

If nArgs > 0 And Application.Version >= 14 Then

is not stopping VBA from entering into the function. Could you send me a screenshot please?

[alex-ifx]

translation:
error while compiling:
named argument not found

[ericremoreynolds]

I get that error when I try to compile the VBA project:

But there is no need to compile it. I do not get the error when I run the functions from the add-in buttons:

Do you confirm that you are getting the error even when running the functions from the add-in buttons?

Thanks for your patience, regards,

Eric.

[alex-ifx]

could it be a language setting problem?

In my localized version of Excel (german version), 12.0 is usually written as 12,0

Furthermore the version number seems to be a string anyway, so I am not sure (VBA newbie) whether you can compare it to an integer.

[ericremoreynolds]

Excellent insight regarding the comma! Yes that is very probably the cause of the problem.

It can be fixed by replacing the line

If nArgs > 0 And Application.Version >= 14 Then

with

If nArgs > 0 And Val(Application.Version) >= 14 Then

Actually you can do that string vs. int comparison in VBA, only apparently it is not clever enough to consider the globalization settings.

If you confirm that it works with this modification then I will include it in the next release.

[alex-ifx]

I think I now have a broken setup and not because of the change you have recommended. I have tried to reproduce my workaround from the first post with a fresh copy of the .xlam file but that does not work (#VALUE!).
Your workaround avoids the initial error but also leads to #VALUE!
Something or more precisely the command line completion seems to work though, because it suggests the function that I have defined.

I have no clue what I did to make this fail so please give me some time to fix my setup before I can give you a final confirmation.

[ericremoreynolds]

Ok, well if you need any more help please just ask!
Regards,
Eric.

[alex-ifx]

Argh! This whole comma/ point/ semicolon thing is a nightmare.

I was following your example that says I have to write =DoubleSum(1,2)

What I actually do need to write instead is =DoubleSum(1;2) to make it work.

I would like to express my gratitude for your timely replies and coming up with a fix so quickly. I really appreciate it. Thank you very much!

Cheers,
Alex

[ericremoreynolds]

Yes it is very irritating how the Excel syntax works differently in different locales. Often the function names change too, for example if the language is Italian the SUM function becomes SOMMA.

I find that for anything but the most basic uses of Excel it is best just to change the system language to US or UK English.

[ericremoreynolds]

However thanks very much for finding that bug with the version number!

Definitely going into the next release.