Hello, I have a problem with a vi. Excel don't start on a computer. configuration: windows 10 Excel 2010 Labview 2019 I've make another VI to test the excel function This Vi works on a computer with excel 2016 and Windows 7 What can I do to run this VI on the pc Windows 10 and excel 2010 Thank you

Thank you for attaching your VI. I do understand that this is an old program, one you probably didn't create, but it is a mess, making it very difficult to understand, difficult to maintain, difficult to improve, but possibly fairly simple to re-create by someone with moderate LabVIEW skills. Here are some suggestions: You have 10 "voie" quantities, with a Control, an Indicator, and a Boolean associated with each. This suggests an "Array of 10" instead of 10 individual Controls/Indicators (much simpler to organize on Front Panel, much simpler to handle on Block Diagram with For Loop and other Array functions). You can associate the Measure (M1), the numeric value (not named on Front Panel), and the the Auto/Manual Switch for each "Voie" by creating a Voie Cluster of three elements. This "binds" the three parts together and again greatly simplifies the code. Why is the Mesure 7 Control given the (displayed) Caption "M10"? Why are you displaying Captions, rather than Labels, especially when the numbering is not consistent? This can only confuse the User, I think. Once you get 10 Numeric Controls, 10 Numeric Indicators, and 10 Boolean Switches simplified to an Array of Clusters (or a Cluster of Arrays, whichever logic makes more sense), your code will immensely simplify and you can get rid of the Frame Sequences and replace it with a State Machine (or something similar) architecture, again making the code much more understandable and easier to modify. Not only do you have Frame sequences, you have them nested to a depth of three! Think Sub-VIs, encapsulate function. A good way to start is to write some high-level documentation (say a page or two) saying What the program is supposed to do. Don't place any "details" in this document, that is, say what the code does, not how to do it (I hope to convince you to do it completely differently!). For example, you would say "Initialize variables by reading data from several files, including config.alc (which initializes the Measure variable), #summary.sta (which initializes some Measurements), initialize plots, ... Note that having one variable with the "Measure Cluster" in it means such things as setting the Plot.Name values for Graph 1 is done with one simple (and small) For Loop. Learn better String Handling. Learn how to use Spreadsheet String to Array to change a multi-line String into an Array of Strings, which allows you to easily fill an Array of Measures from an Array of values read from a file. Use sub-VIs to "hide" irrelevant code that does initialization, reformatting, things that are necessary but not central to the essential task you are doing (such as initialization!). Use the Error Line everywhere you can to ensure that (a) you'll "trap" (and know about) any errors that may arise, (b) you will specify in an obvious way the order you need for your code to work properly, and (c) having a horizontal Error Line will help keep your Block Diagram "neat" and easier to understand. When you are finally ready to use Excel, use the Report Generation Toolkit. If it is not included in your License, purchase it -- it will repay you by allowing you to easily read/write Excel, works with Windows 10, works with LabVIEW 2019, works with Excel 2013 and later (and probably earlier), is currently supported by NI, etc. Bob Schor

LabVIEW

excel don't start with a computer, but the VI works on another computer

Solved!

There's a very nice example that will show you some of the capabilities of the Report Generation Toolkit (it absolutely requires this toolkit). Open the Forum, and in the Search box type the words "Revised Example " and stop. Let it find some matches, and choose the Obvious One (it mentions "Excel"). Note that this might have a broken Run arrow -- Microsoft changed Excel, but the fix is fairly easy and has been documented in the Forum, as well.

Bob Schor