08-25-2008 08:14 AM
08-25-2008 08:19 AM
Sorry we dont understand that language.
08-25-2008 08:44 AM - edited 08-25-2008 08:44 AM
Hi Boone301,
can you explain a bit more in detail? When do you get the bug? What do you insert into Excel? Why do you think it´s a bug, what happens?
Mike
08-26-2008 03:59 AM
Hi, you can paste a screenshot to describe your findings, and I also introduce the Excel Macro Example.vi, this example can help you learn how to deal with ActiveX.
Best wishes,
08-26-2008 04:05 AM - edited 08-26-2008 04:08 AM
Peterpan,
Have you forgot the attachment?
Edit: Oops sorry just now understood that its in Examples Finder.
08-26-2008 09:23 PM
Sorry, Mathon.
I didn't see any attachment in your reply.
08-27-2008 02:36 AM
Dear all,
As the picture.
Boone
08-27-2008 03:10 AM
Hi Boone,
Whenever you wanna use ActiveX to get the method or properties of the object, be sure to use the Automation Open.vi first, then use the output reference to call the objects' property or method.
Best wishes,
08-27-2008 10:10 AM
Peterpan wrote:Hi Boone,
Whenever you wanna use ActiveX to get the method or properties of the object, be sure to use the Automation Open.vi first, then use the output reference to call the objects' property or method.
Best wishes,
That is only necessary if you need to instantiate the ActiveX object programmatically. Clearly the user has an ActiveX container, so the object has already been created, and Automation Open is not necessary and would actually provide a separate object alltogether.
To Boone: What kind of ActiveX object did you insert in the container? I can't quite tell from the screenshot.
08-31-2008 12:22 AM