Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
DCOM98 and EXCEL2000 collision
Try using late binding.
Instead of Dim xl as Excel.Application use Dim xl as Object then instantiate the object by using Set xl = CreateObject("Excel.Application") Don't forget to remove the Excel reference from your project otherwise you'll be defeating the point of this. -- Regards, Bill Lunney www.billlunney.com "Milko Koparanov" wrote in message ... I've written a short procedure in VS6, which opens a new Excel2000 application and populates a Range object: Private Sub Populate() Dim xl As Excel.Application, i as Integer Set xl = New Excel.Application xl.Visible = True xl.Workbooks.Add For i = 1 To 100 xl.Cells(i, i) = i ^ 2 Next i Set xl = Nothing End Sub It works perfectly under WindowsXP and Windows98. But if you have DCOM98 installed on W98 OS, it breaks on xl.Cells(i, i) = i ^ 2 row, messaging an AUTOMATION ERROR -2147417848(80010108). It works exactly the same way with or without Office2000 SP3, and from a VBA module of MS Office2000. Thanks for any suggestion why this could happen! Milko Koparanov |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
why Excel2000 don't allow to write | Excel Discussion (Misc queries) | |||
Excel2000: The latest value | Excel Worksheet Functions | |||
Printing in Excel2000? | Excel Worksheet Functions | |||
DCOM98 and EXCEL2000 collision | Excel Programming | |||
Excel2000 VB Help Problem! | Excel Programming |