I have an ATL/COM project that I'm developing which have a number of functions that can be accessed in Excel as worksheets functions. All these functions so far belong to one object with the associated Interface. This all works great.
But when I added a second object and used the Tools-Add-ins-Automation to add it, its interface did not show up in the function categories and its functions are not accessible. The first object is visible and accessable though. Is there something I'm missing? or can excel only use 1 interface? ... Any help would be appreciated.

Thanks ...

Hi Gary,

I am also in fight with the COM interface. I also can't get a second one
visible. And I have a question for you. Are you able to make any
modifications to the sheet from inside your COM to the sheet that you are
calling the COM-based functions from?

As an example a SetValue on a Range always seems to fail. I can make
formatting changes from the COM, but SetValue gives me an exception with
error code 0x800a03ec. I have turned the code upside down in many hours of
testing, and it seems that the "calling sheet" is locked or something for
updating cell content. Do you have any idea why I am having that problem?
The underlying task is for the COM to fill in a range with values,
calculated in the COM and to go into a range specified in the function call.

Thanks!

Uwe


"Gary C" wrote in message
...
I have an ATL/COM project that I'm developing which have a number of
functions that can be accessed in Excel as worksheets functions. All these
functions so far belong to one object with the associated Interface. This
all works great.
But when I added a second object and used the Tools-Add-ins-Automation
to add it, its interface did not show up in the function categories and
its functions are not accessible. The first object is visible and
accessable though. Is there something I'm missing? or can excel only use 1
interface? ... Any help would be appreciated.

Thanks ...

Hi Uwe,

As an example a SetValue on a Range always seems to fail. I can make
formatting changes from the COM, but SetValue gives me an exception with
error code 0x800a03ec. I have turned the code upside down in many hours of
testing, and it seems that the "calling sheet" is locked or something for
updating cell content. Do you have any idea why I am having that problem?
The underlying task is for the COM to fill in a range with values,
calculated in the COM and to go into a range specified in the function call.

It's a long-standing given that functions called from the worksheet can only
return values, they can't change the contents of other cells.

Regards

Stephen Bullen
Microsoft MVP - Excel
www.BMSLtd.ie

Forgive me Stephen, I never had to deal with these matters, ie Office
programming. Until today I have managed to get anything going through
programming, there has got to be a way. I think I might be able to copy the
content of the active sheet into a new sheet and do my voodoo there, but
it's just not clean to the end-user. So I am not quite giving up on this. Is
the deep reason for not being able to update the sheet, from which you are
calling the XLL, that it is somehow "write-protected" and I should start
fishing in that neighborhood?

Thanks a mille!

Uwe


"Stephen Bullen" wrote in message
...
Hi Uwe,

As an example a SetValue on a Range always seems to fail. I can make
formatting changes from the COM, but SetValue gives me an exception with
error code 0x800a03ec. I have turned the code upside down in many hours
of
testing, and it seems that the "calling sheet" is locked or something for
updating cell content. Do you have any idea why I am having that problem?
The underlying task is for the COM to fill in a range with values,
calculated in the COM and to go into a range specified in the function
call.

It's a long-standing given that functions called from the worksheet can
only
return values, they can't change the contents of other cells.

Regards

Stephen Bullen
Microsoft MVP - Excel
www.BMSLtd.ie

Hi Um,

So I am not quite giving up on this.

Good luck!

Is
the deep reason for not being able to update the sheet, from which you are
calling the XLL, that it is somehow "write-protected" and I should start
fishing in that neighborhood?

No, it's because Excel is protecting is recalc tree.

Regards

Stephen Bullen
Microsoft MVP - Excel
www.BMSLtd.ie

Thanks Stephen,

that helps me understand the underlying problem!

Uwe

"Stephen Bullen" wrote in message
...
Hi Um,

So I am not quite giving up on this.

Good luck!

Is
the deep reason for not being able to update the sheet, from which you
are
calling the XLL, that it is somehow "write-protected" and I should start
fishing in that neighborhood?

No, it's because Excel is protecting is recalc tree.

Regards

Stephen Bullen
Microsoft MVP - Excel
www.BMSLtd.ie