PC Review


Reply
Thread Tools Rate Thread

C# COM given "#NAME" error

 
 
Torben Laursen
Guest
Posts: n/a
 
      20th Mar 2007
I have A COM add-in for Excel 2003 that is beeing used without any problems
on a number of computers.

However one of my customers cannot get it to work.
When he tryes to call one of the UDF in the COM he get the error: #NAME.

The COM seens to be installed correct. It addes a menu to Excel and he can
use the winforms that are in the COM.
Also there is no disabled items in Excel (Under Hep/About/Disabled items)
So everything seems to work except the user defined functions inside the COM

Can anyone give me any hints about how I solve this problem?

Thanks
Torben


 
Reply With Quote
 
 
 
 
NickHK
Guest
Posts: n/a
 
      20th Mar 2007
Torben,
Just a guess: Are you sure the user is using the correct function names ?

NickHK

"Torben Laursen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have A COM add-in for Excel 2003 that is beeing used without any

problems
> on a number of computers.
>
> However one of my customers cannot get it to work.
> When he tryes to call one of the UDF in the COM he get the error: #NAME.
>
> The COM seens to be installed correct. It addes a menu to Excel and he can
> use the winforms that are in the COM.
> Also there is no disabled items in Excel (Under Hep/About/Disabled items)
> So everything seems to work except the user defined functions inside the

COM
>
> Can anyone give me any hints about how I solve this problem?
>
> Thanks
> Torben
>
>



 
Reply With Quote
 
Torben Laursen
Guest
Posts: n/a
 
      20th Mar 2007
Nick,

Thanks, yes he send me screendumps.

Torben


"NickHK" <(E-Mail Removed)> wrote in message
news:uVleG%(E-Mail Removed)...
> Torben,
> Just a guess: Are you sure the user is using the correct function names ?
>
> NickHK
>
> "Torben Laursen" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I have A COM add-in for Excel 2003 that is beeing used without any

> problems
>> on a number of computers.
>>
>> However one of my customers cannot get it to work.
>> When he tryes to call one of the UDF in the COM he get the error: #NAME.
>>
>> The COM seens to be installed correct. It addes a menu to Excel and he
>> can
>> use the winforms that are in the COM.
>> Also there is no disabled items in Excel (Under Hep/About/Disabled items)
>> So everything seems to work except the user defined functions inside the

> COM
>>
>> Can anyone give me any hints about how I solve this problem?
>>
>> Thanks
>> Torben
>>
>>

>
>



 
Reply With Quote
 
Peter T
Guest
Posts: n/a
 
      20th Mar 2007
Another guess, any simimilarly named functions around anywhere

Regards,
Peter T

"Torben Laursen" <(E-Mail Removed)> wrote in message
news:uS#(E-Mail Removed)...
> Nick,
>
> Thanks, yes he send me screendumps.
>
> Torben
>
>
> "NickHK" <(E-Mail Removed)> wrote in message
> news:uVleG%(E-Mail Removed)...
> > Torben,
> > Just a guess: Are you sure the user is using the correct function names

?
> >
> > NickHK
> >
> > "Torben Laursen" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> I have A COM add-in for Excel 2003 that is beeing used without any

> > problems
> >> on a number of computers.
> >>
> >> However one of my customers cannot get it to work.
> >> When he tryes to call one of the UDF in the COM he get the error:

#NAME.
> >>
> >> The COM seens to be installed correct. It addes a menu to Excel and he
> >> can
> >> use the winforms that are in the COM.
> >> Also there is no disabled items in Excel (Under Hep/About/Disabled

items)
> >> So everything seems to work except the user defined functions inside

the
> > COM
> >>
> >> Can anyone give me any hints about how I solve this problem?
> >>
> >> Thanks
> >> Torben
> >>
> >>

> >
> >

>
>



 
Reply With Quote
 
=?Utf-8?B?UmljY2FyZG8=?=
Guest
Posts: n/a
 
      20th Mar 2007

hello, I have had a similar problem.

in my case the issue was that excel not using the correct version of the
..net framework.

I have resolved adding the text file excel.exe.config in the office folder
with the following rows
<configuration>
<startup>
<supportedRuntime version= " v2.0.50727 "/>
</startup>
</configuration>

"Torben Laursen" wrote:

> I have A COM add-in for Excel 2003 that is beeing used without any problems
> on a number of computers.
>
> However one of my customers cannot get it to work.
> When he tryes to call one of the UDF in the COM he get the error: #NAME.
>
> The COM seens to be installed correct. It addes a menu to Excel and he can
> use the winforms that are in the COM.
> Also there is no disabled items in Excel (Under Hep/About/Disabled items)
> So everything seems to work except the user defined functions inside the COM
>
> Can anyone give me any hints about how I solve this problem?
>
> Thanks
> Torben
>
>
>

 
Reply With Quote
 
Torben Laursen
Guest
Posts: n/a
 
      21st Mar 2007
Riccardo,
Thanks for the feedback. But it did not solve the problem.

Torben

"Riccardo" <(E-Mail Removed)> wrote in message
news:1940CC6C-0CC5-494E-ABBE-(E-Mail Removed)...
>
> hello, I have had a similar problem.
>
> in my case the issue was that excel not using the correct version of the
> .net framework.
>
> I have resolved adding the text file excel.exe.config in the office folder
> with the following rows
> <configuration>
> <startup>
> <supportedRuntime version= " v2.0.50727 "/>
> </startup>
> </configuration>
>
> "Torben Laursen" wrote:
>
>> I have A COM add-in for Excel 2003 that is beeing used without any
>> problems
>> on a number of computers.
>>
>> However one of my customers cannot get it to work.
>> When he tryes to call one of the UDF in the COM he get the error: #NAME.
>>
>> The COM seens to be installed correct. It addes a menu to Excel and he
>> can
>> use the winforms that are in the COM.
>> Also there is no disabled items in Excel (Under Hep/About/Disabled items)
>> So everything seems to work except the user defined functions inside the
>> COM
>>
>> Can anyone give me any hints about how I solve this problem?
>>
>> Thanks
>> Torben
>>
>>
>>



 
Reply With Quote
 
Torben Laursen
Guest
Posts: n/a
 
      22nd Mar 2007
I have solved the problem.

It turned out that the customer has installed Norton internet security 2007
and it was blocking the COM.
The solution is to disable the office plugin in Norton.

Torben

"Torben Laursen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Riccardo,
> Thanks for the feedback. But it did not solve the problem.
>
> Torben
>
> "Riccardo" <(E-Mail Removed)> wrote in message
> news:1940CC6C-0CC5-494E-ABBE-(E-Mail Removed)...
>>
>> hello, I have had a similar problem.
>>
>> in my case the issue was that excel not using the correct version of the
>> .net framework.
>>
>> I have resolved adding the text file excel.exe.config in the office
>> folder
>> with the following rows
>> <configuration>
>> <startup>
>> <supportedRuntime version= " v2.0.50727 "/>
>> </startup>
>> </configuration>
>>
>> "Torben Laursen" wrote:
>>
>>> I have A COM add-in for Excel 2003 that is beeing used without any
>>> problems
>>> on a number of computers.
>>>
>>> However one of my customers cannot get it to work.
>>> When he tryes to call one of the UDF in the COM he get the error: #NAME.
>>>
>>> The COM seens to be installed correct. It addes a menu to Excel and he
>>> can
>>> use the winforms that are in the COM.
>>> Also there is no disabled items in Excel (Under Hep/About/Disabled
>>> items)
>>> So everything seems to work except the user defined functions inside the
>>> COM
>>>
>>> Can anyone give me any hints about how I solve this problem?
>>>
>>> Thanks
>>> Torben
>>>
>>>
>>>

>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Error messages: "Winsck," "Status," and "Unable to open dialog" =?Utf-8?B?Sm9u?= Microsoft Windows 2000 0 17th Dec 2003 10:46 PM
Manual "Windows Update" produces "ActiveX/active scripting" error message even with "LOW" security level setting in "Trusted" Zone Ray2 Windows XP Help 1 14th Nov 2003 06:50 PM
Error messages: "Winsck," "Status," and "Unable to open dialog" =?Utf-8?B?Sm9u?= Microsoft Windows 2000 0 9th Nov 2003 06:16 AM
Error messages: "Winsck," "Status," and "Unable to open dialog" =?Utf-8?B?Sm9u?= Microsoft Windows 2000 0 28th Oct 2003 12:51 AM
Error messages: "Winsck," "Status," and "Unable to open dialog" =?Utf-8?B?Sm9u?= Microsoft Windows 2000 0 16th Oct 2003 03:16 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 10:28 AM.