LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Excel 2010 and labview 2010

Solved!
Go to solution

I think this may have been covered, but has anyone noticed any differences in the ActiveX properties or methods in labview when working with excel 2007 as opposed to excel 2010? I know at one point Microsoft had changed a few things from excel '97 to '2003 and instead of selecting "value" in your method, you now have to choose "value 2". Does the same hold true for excel 2010? I am currently using excel 2007 at work and 2000 at home and when I open my code at home, my invoke nodes "have bad wires" yet all required inputs are correct. Same code on excel 2007; no bad wires and the code will run. I am just curious if anyone has tried to use labview 2010 and excel 2010 together and did it work? I'm opening 1 workbook and writing to 4 different excel sheets using WinXP, excel 2007 at work and have windows 7 and want to use excel 2010 at home and would prefer no problems or at the very least know what some potential problems are. Sorry if this confusing. I think this is the best way I can explain it as I haven't gotten MY head wrapped around it yet.  I just don't want to write the same code twice for the different versions of excel. (write and test at home, then re-write at work)  

 

http://digital.ni.com/public.nsf/allkb/177D720A428CA72B862567EC00757F0C

this is one example of what I'm talking about

 

 

 

0 Kudos
Message 1 of 17
(5,927 Views)
Solution
Accepted by topic author Myke

Myke,

 

While I don't have excel 2010 available to try-and-see, Microsoft (and MSDN) has a huge amount of information regarding calls in all versions of Excel. 

 

Excel 2010 development resources: http://msdn.microsoft.com/en-us/library/ee658205(office.14).aspx

Excel 2007 development resources: http://msdn.microsoft.com/en-us/library/bb979621(v=office.12).aspx

 

Hopefully this helps you get started, as I do not have access to excel 2010. Let me know if it works for you. 

 

Regards,

Kyle Mozdzyn

Applications Engineering

National Instruments

Regards,

Kyle M.
Applications Engineering
National Instruments
Message 2 of 17
(5,898 Views)

Kyle,

Thanks for the response. While reading all that stuff on those website is alot like tracing the flight pattern of your average housefly, I did manage to make sense of some of it. I think it will work and I'm about to buy a copy to office 2010 to try and prove it. There were some improvements to excel 2010 but they shouldn't affect how things get called and referenced.

 

 

 

Myke

 

0 Kudos
Message 3 of 17
(5,892 Views)

Myke, 

 

Glad that was able to help a bit. Some of the MSDN stuff is quite hard to follow/over my head, but glad you were able to make sense of it. Best of luck, and please keep us posted on compatibility. 

 

Regards

Kyle Mozdzyn

Applications Engineering

National Instruments

Regards,

Kyle M.
Applications Engineering
National Instruments
0 Kudos
Message 4 of 17
(5,872 Views)

Will do. hopefully I won't run into too many problems if any. I hate to just ask questions and not help, so here's my chance. LOL

 

 

0 Kudos
Message 5 of 17
(5,870 Views)

Kyle,

since we are talking about calls, methods, and such, I was wondering if you or someone else could take a look at this code and see what I'm doing wrong. The program itself was much bigger at one time, I think I may have narrowed it to this because I keeo getting a write to excel error. I'm using winxp, office 2007 and reading from a .CSV file to simulate data gathering. on the csv sheet for the ranges are B849:N866 for the "floor" skipping over two sheets and using D850:L865 for the "right wall". then of course I am using just a simple range to write it all to the sheet(s).

 

stacking.csv is where the data is coming from

WFC automation sheet is where it's going.

 

0 Kudos
Message 6 of 17
(5,845 Views)

here is the other that goes with it that is where the problem is.

 

 

0 Kudos
Message 7 of 17
(5,844 Views)

Myke, 

 

I took a look at your code, and the issue is coming from when you close the 'sheets' reference before using it again, making it an invalid reference. Deleting the red-boxed close reference will fix the issue.


After doing that, youll get a second error for invalid reference (also boxed in red), which is because sheet 4 doesnt exist.

 

Hope this gets you what you want. 

 

Regards,

 

Kyle Mozdzyn

Applications Engineering

National Instruments 

 

Regards,

Kyle M.
Applications Engineering
National Instruments
Message 8 of 17
(5,810 Views)

Kyle,

Thanks for looking at that. I guess I just got a little happy with the close reference function. I'll try it and see what I come up with.

 

 

0 Kudos
Message 9 of 17
(5,762 Views)

Ok Kyle,

I did what you suggested and it worked beautifully, even writing to sheet number 4 on the wfc automation workbook. I'm uploading a pic and the red box and line are the pieces I got rid of and did a little rewiring.

 

BTW, I got my copy of office 2010 and will be installing it in a day or two. I'll post anything that I find and or notice.

0 Kudos
Message 10 of 17
(5,755 Views)