The name ... either conflicts with a valid range reference or isinvalid for Excel.

[Greg Lovern]

One of my users is getting the following error. He sent me a picture
so I have the exact text:

==========================================================
[Microsoft Office Excel]
(exclamation point)
The name, ClickedMatchButton("Button 664"), either conflicts with a
valid range reference or is invalid for Excel. The name has been
replaced with _1ClickedMatchButton__Button_664.

You may still need to manually update any references to this name used
in VBA code or as text arguments in functions. You must close and
reopen the workbook before these changes take effect.

<OK> <OK to All>
==========================================================

(btw the "1" is there in the error message; it's not a typo.)

We're both using Excel 2007.

The code is NOT creating defined names. The code is creating forms
(not ActiveX) buttons, and setting their OnAction properties to send
their own button name as a parameter to a function:

strButtonNameArg = """" & btnMatch.Name & """" 'must wrap with
doublequote characters.
btnMatch.OnAction = "'" & strThisWorkbookName &
"'!'ClickedMatchButton(" & strButtonNameArg & ")'"

(the reason I'm doing it that way is because we have too many long
parameters for OnAction's 255-character limit, so I'm putting the real
parameters in the buttons' AlternativeText properties, which have a
4,095-character limit (in VBA, though only 255 manually), then parsing
the parameters out of each button's AlternativeText property when
called, using commas as delimiters and doubling any commas in the
actual parameters to escape them.)

It all works fine for me, and fine for others except for the one
person, and fine him too most of the time. He's gotten the error twice
(with different button numbers each time).

I don't see any reference to this error in this newsgroup. I found
three on the web, but two of them have no solutions, and the third is
in Thai, which unfortunately Babelfish doesn't translate to English:

http://www.fftodayforums.com/forum/index.php?showtopic=281892
http://www.thaivi.com/webboard/archive.php/o_t__t_1294__start_6420__index.html
http://www.youneedabudget.com/forum/viewtopic.php?f=5&t=1520&p=10526


I haven't been able to reproduce this error myself, though I've done
exactly what that user said he'd done, with the exact same input data.
We're both using Excel 2007, and both on Windows XP/SP2.


Any suggestions?


Thanks,

Greg

 

[Greg Lovern]

Now another user has reported this error, though with a different
button number.

Any suggestions? I still haven't been able to repro.

Greg

 

[Greg Lovern]

Two users have now reported this error happening when the code wasn't
even running, while they had task-switched away from Excel and were
working in other applications.

Any suggestions? I still haven't been able to repro, though I've tried
everything every user who has reported it says they were doing at the
time.


Greg

Now another user has reported this error, though with a different
button number.

Any suggestions? I still haven't been able to repro.

Greg

One of my users is getting the following error. He sent me a picture
so I have the exact text:

==========================================================
[Microsoft Office Excel]
(exclamation point)
The name, ClickedMatchButton("Button 664"), either conflicts with a
valid range reference or is invalid for Excel. The name has been
replaced with _1ClickedMatchButton__Button_664.

You may still need to manually update any references to this name used
in VBA code or as text arguments in functions. You must close and
reopen the workbook before these changes take effect.

<OK> <OK to All>
==========================================================

(btw the "1" is there in the error message; it's not a typo.)

We're both using Excel 2007.

The code is NOT creating defined names. The code is creating forms
(not ActiveX) buttons, and setting their OnAction properties to send
their own button name as a parameter to a function:

strButtonNameArg = """" & btnMatch.Name & """" 'must wrap with
doublequote characters.
btnMatch.OnAction = "'" & strThisWorkbookName &
"'!'ClickedMatchButton(" & strButtonNameArg & ")'"

(the reason I'm doing it that way is because we have too many long
parameters for OnAction's 255-character limit, so I'm putting the real
parameters in the buttons' AlternativeText properties, which have a
4,095-character limit (in VBA, though only 255 manually), then parsing
the parameters out of each button's AlternativeText property when
called, using commas as delimiters and doubling any commas in the
actual parameters to escape them.)

It all works fine for me, and fine for others except for the one
person, and fine him too most of the time. He's gotten the error twice
(with different button numbers each time).

I don't see any reference to this error in this newsgroup. I found
three on the web, but two of them have no solutions, and the third is
in Thai, which unfortunately Babelfish doesn't translate to English:

I haven't been able to reproduce this error myself, though I've done
exactly what that user said he'd done, with the exact same input data.
We're both using Excel 2007, and both on Windows XP/SP2.

Any suggestions?

Greg

 

[iThomasM]

We are also having this error in Excel 2007. After it came up, the
document formatting was all lost.

The documents are big, but full of words, numbers and formatting. No
forms or programming.

Person it happened to is on a Sony running Vista and Excel 2007. The
computer connects to Windows Update so it should be up to date. Norton
360 us also protecting the machine.

WIth multiple setups like this, the only difference I can see off hand
is the brand of computer.

Thoughts?
Help?

 

[cameronhudson8]

I saved as an XLSX file a document that had been an XLS file. This message appears when I open the new XLSX file, and occasionally appears spontaneously while the file is open (or for an unknown reason, at least).

It's funny because Excel suggested that I save the file as XLSX to improve compatibility.

 

[witek]

I saved as an XLSX file a document that had been an XLS file. This message appears when I open the new XLSX file, and occasionally appears spontaneously while the file is open (or for an unknown reason, at least).

It's funny because Excel suggested that I save the file as XLSX to improve compatibility.

whatever was a valid name in Excel 2003 i.e. sec1 is now a valid cell
reference.

start looking...

 

[phillip.vanwagoner]

This is happening to me now, on a Mac, in an .xls file, so it doesn't seem to be an xlsx file issue or a Windows issue. Did anyone else have any luck figuring it out?