
Signature
Regards,
Alvin Bruney - ASP.NET MVP
[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
Right, but only after the installation of Excel itself, not its Interop
assembly. The latter does not register any ProgIDs in the registry, it
merely instructs the framework on proper creation of runtime-callable
wrappers.

Signature
Sincerely,
Dmytro Lapshyn [Visual Developer - Visual C# MVP]
> Then how does it know what to create? It must know what an
> Excel.Application is right? That knowledge comes only after an
[quoted text clipped - 29 lines]
>>>>>
>>>>> Marina
Alvin Bruney [MVP - ASP.NET] - 01 Jul 2005 01:09 GMT
I see what you are saying. That's correct. I change my advice to this:
>>in order to call createobject on the excel application, excel must be
>>correctly installed on the target system.

Signature
Regards,
Alvin Bruney - ASP.NET MVP
[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
> Right, but only after the installation of Excel itself, not its Interop
> assembly. The latter does not register any ProgIDs in the registry, it
[quoted text clipped - 34 lines]
>>>>>>
>>>>>> Marina