Importing data from Excel 2000

[Elmosca]

Hi, I've developped an application which imports some data cells from excel.
In Win XP and Excel XP it works pretty good, but in a Win98 Excel 2000
system it does'nt. The error exception I get is:

Exception Details: System.Runtime.InteropServices.COMException: COM
object with CLSID {00024500-0000-0000-C000-000000000046} is either not
valid or not registered.

How can I solve this problem? Any ideas? TIA

Regards,

[Paul Clement]

On Mon, 7 Oct 2002 18:17:48 +0200, "Elmosca" <elmosca@terra.es> wrote:

¤ Hi, I've developped an application which imports some data cells from excel.
¤ In Win XP and Excel XP it works pretty good, but in a Win98 Excel 2000
¤ system it does'nt. The error exception I get is:
¤
¤ Exception Details: System.Runtime.InteropServices.COMException: COM
¤ object with CLSID {00024500-0000-0000-C000-000000000046} is either not
¤ valid or not registered.
¤

It's identifying the Excel.Application object. Are you sure that Excel 2000 is installed properly on
this machine? You can probably verify this by doing a quick test automating Excel from another
VBA application such as Word.


Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)

[Elmosca]

Excel 2000 is installed properly. And this problem happens in every computer
with Excel 2000. I think the problem is in the application.
My application has a reference to Microsoft Excel 10.0 Object Library v1.4
and to the Office 10.0 one. Maybe this depends on the excel version.
I've tested the application in:
- my computer (developer) (wXP, excelXP)
- 1 computer wXP, excelXP
- 2 computers w98, excel2000

It only works in the computers with excel XP, I'm lost

Regards,



"Paul Clement" <UseAdddressAtEndofMessage@swspectrum.com> escribió en el
mensaje news:7al3qusoncdi4auoo7dfsd0btco0ao172t@4ax.com...
> On Mon, 7 Oct 2002 18:17:48 +0200, "Elmosca" <elmosca@terra.es> wrote:
>
> ¤ Hi, I've developped an application which imports some data cells from
excel.
> ¤ In Win XP and Excel XP it works pretty good, but in a Win98 Excel 2000
> ¤ system it does'nt. The error exception I get is:
> ¤
> ¤ Exception Details: System.Runtime.InteropServices.COMException: COM
> ¤ object with CLSID {00024500-0000-0000-C000-000000000046} is either not
> ¤ valid or not registered.
> ¤
>
> It's identifying the Excel.Application object. Are you sure that Excel
2000 is installed properly on
> this machine? You can probably verify this by doing a quick test
automating Excel from another
> VBA application such as Word.
>
>
> Paul ~~~ pclement@ameritech.net
> Microsoft MVP (Visual Basic)

[Rune Bivrin]

"Elmosca" <elmosca@terra.es> wrote in news:3da1dc14$1@10.1.10.29:

> Excel 2000 is installed properly. And this problem happens in every
> computer with Excel 2000. I think the problem is in the application.
> My application has a reference to Microsoft Excel 10.0 Object Library
> v1.4 and to the Office 10.0 one. Maybe this depends on the excel
> version. I've tested the application in:
> - my computer (developer) (wXP, excelXP)
> - 1 computer wXP, excelXP
> - 2 computers w98, excel2000
>
> It only works in the computers with excel XP, I'm lost
>
> Regards,
>
Office 10.0 is Office XP, as far as I know. What is probably happening is
that the class is queried for an interface id which is implemented by the
Excel XP version of the class, but not by the Excel 2000 version. I don't
have Office XP myself, but you could probably nverify this with OLE
Viewer.

I'm not completely familiar with the workings of COM interop yet, but I'd
proceed as follows:

Set a reference to the Excel 2000 object library. It's in (on my machine)
'C:\Program Files\Microsoft Office\Office\EXCEL9.OLB'. If that doesn't do
the trick:

Uninstall Office XP and install Office 2000.

--
Rune Bivrin
- OOP since 1989
- SQL Server since 1990
- VB since 1991

[Elmosca]

But then will work for Excel 2000 but not for other versions, won't it? I
want an application which opens an excel file, whatever the version...


"Rune Bivrin" <rune@bivrin.com> escribió en el mensaje
news:Xns92A0E603733F3runebivrincom@209.1.14.29...
> "Elmosca" <elmosca@terra.es> wrote in news:3da1dc14$1@10.1.10.29:
>
> > Excel 2000 is installed properly. And this problem happens in every
> > computer with Excel 2000. I think the problem is in the application.
> > My application has a reference to Microsoft Excel 10.0 Object Library
> > v1.4 and to the Office 10.0 one. Maybe this depends on the excel
> > version. I've tested the application in:
> > - my computer (developer) (wXP, excelXP)
> > - 1 computer wXP, excelXP
> > - 2 computers w98, excel2000
> >
> > It only works in the computers with excel XP, I'm lost
> >
> > Regards,
> >
> Office 10.0 is Office XP, as far as I know. What is probably happening is
> that the class is queried for an interface id which is implemented by the
> Excel XP version of the class, but not by the Excel 2000 version. I don't
> have Office XP myself, but you could probably nverify this with OLE
> Viewer.
>
> I'm not completely familiar with the workings of COM interop yet, but I'd
> proceed as follows:
>
> Set a reference to the Excel 2000 object library. It's in (on my machine)
> 'C:\Program Files\Microsoft Office\Office\EXCEL9.OLB'. If that doesn't do
> the trick:
>
> Uninstall Office XP and install Office 2000.
>
> --
> Rune Bivrin
> - OOP since 1989
> - SQL Server since 1990
> - VB since 1991

[Rune Bivrin]

"Elmosca" <elmosca@terra.es> wrote in news:3da1eeac@10.1.10.29:

> But then will work for Excel 2000 but not for other versions, won't
> it? I want an application which opens an excel file, whatever the
> version...
>

Well, can't test it, but Excel XP should be compatible with Excel 2000.
Otherwise, you should stick to late binding with CreateObject(). Not as
cool, but less picky on versions.

--
Rune Bivrin
- OOP since 1989
- SQL Server since 1990
- VB since 1991

[Rune Bivrin]

"Elmosca" <elmosca@terra.es> wrote in news:3da20096@10.1.10.29:

> Yes, it's true. That's the answer... thanks!
>
> Bruno
>
>

Glad I could help!

--
Rune Bivrin
- OOP since 1989
- SQL Server since 1990
- VB since 1991

[Elmosca]

Yes, it's true. That's the answer... thanks!

Bruno

"Rune Bivrin" <rune@bivrin.com> escribió en el mensaje
news:Xns92A1136E91B3runebivrincom@209.1.14.29...
> "Elmosca" <elmosca@terra.es> wrote in news:3da1eeac@10.1.10.29:
>
> > But then will work for Excel 2000 but not for other versions, won't
> > it? I want an application which opens an excel file, whatever the
> > version...
> >
>
> Well, can't test it, but Excel XP should be compatible with Excel 2000.
> Otherwise, you should stick to late binding with CreateObject(). Not as
> cool, but less picky on versions.
>
> --
> Rune Bivrin
> - OOP since 1989
> - SQL Server since 1990
> - VB since 1991