office 2010 labview 2010

[Stigwood]

Trying to get a Excel generation program to work with Office 2010 - and I have issues with Active X nodes - see attachment. I have read similar posts, but not sure how to solve this issue.

Thanks

[smercurio_fc]

What connection are you trying to make? The FormatCondition node has all of the parameters as outputs. It doesn't accept any inputs. Are you saying one of them should be an input?

[Stigwood]

I am not really to sure!

The attached diagram is where the error is.

Basically I'm trying to build an app which takes teh data picked up from a SQL table and then display the results in Excel.

James

[smercurio_fc]

The problem is that the Add method is not interpreting the return value properly. It's treating is a variant, rather than as an ActiveX class. This appears to be an issue with the Office 2010 ActiveX interface, since it works just fine with Office 2003 (which is what I have) and LV 2010.

In this case you'll need to typecast the variant to the proper ActiveX class:

NOTE: My picture is a mock-up, since I'm showing you to take the Add terminal and wire that to a Variant to Data function. To make that picture I have a variant constant hiding behind the Invoke node in order to show the variant wire that would go from the Add method to the Variant to Data function. As you can see, in my case the Add returns an ActiveX datatype (it's that teal color, rather than the funny purple used for variants).

[Stigwood]

smercurio_fc,

Many thanks for your help on this,

This gives me more issues further down the chain. If I attach the VI would you mind having a look at it?

Cheers,

James

[smercurio_fc]

All that I can do is try, and if I can't figure it out someone can take a crack at it.   Go ahead and post your VI and indicate what your problem is. 

[Stigwood]

Thanks Mate

[smercurio_fc]

Well, your code is hard to follow. Plus, all of the subVIs are missing. What exactly is the problem?

[Stigwood]

Sorry about that, the main error was where you had suggested.

Right now we have rolled back to office 2003 - so all errors have gone.

The issue was the variants out of the property nodes showing a broken wire.