06-04-2007 02:46 PM
06-04-2007 02:52 PM
You can open the "write to spreadsheet file" and you can see that all it basically does is use "array to spreadsheet string" the write the resulting string to the file. You can do that yourself if you have a more complex situation! 🙂
In LabVIEW, a "spreadheet" is nothing more than an ASCII formatted table with columns separated by tabs (by default) and rown separated by linefeeds. It has nothing to to with any proprietary binary format such as excel.
06-04-2007 03:02 PM
06-04-2007 03:49 PM
06-04-2007 03:50 PM - edited 06-04-2007 03:50 PM
Message Edited by unknown00 on 06-04-2007 03:51 PM
06-04-2007 04:09 PM - edited 06-04-2007 04:09 PM
No, it's not good!
Since there is no data dependency between the two file writes, there is no way to tell which one occurs first. LabVIEW is dataflow driven and does not necessarily execute left-to-right.
For a quick fix you could wire the error-out of the one that should happen first to the error-in of the second. This ensures data dependncy and the second one cannot start until it recevied data on the error wire, which can only happen when the first instance finishes.
Why don't you concatenate the two strings and use only a single file operation as in my earlier suggestion?
Other comment:. Assuming that the top array in the cluster is the same for all array elements, you can probably delete the "index array" and disable indexing at the output tunnel of of the upper array leaving the FOR loop. (If the top arrays differ, a lot of the code would not make sense because you would be throwing away most of the data)
Message Edited by altenbach on 06-04-2007 02:10 PM
06-05-2007 08:39 AM
06-05-2007 09:35 AM
I would flip the inputs to the "concatenate strings" It seems more likely that the column headers should be written first.
How does the output look like if you run it?
06-05-2007 09:40 AM
06-05-2007 09:56 AM