LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Bug in Write To Spreadsheet File VI

Solved!
Go to solution

Hello,

There is a bug in the Write To Spreadsheet File VI.

 

The delimiter field is said in the documentation to default to \t, while in reality it defaults to nothing -- which is useless.

 

By the way defaulting to comma is in my opinion a better choice, but that is secondary.

 

Guillaume

0 Kudos
Message 1 of 9
(3,685 Views)

Guillaume,

 

what version of LV are you using?

Nevertheless, i think that you are incorrect about this regardless of the LV version you are using. Please do the following:

1. Create a new VI, drop the "Write to spreadsheet file.vi". The Context Help states that \t is the default value for the delimiter.

2. Create a constant for the delimiter. Indeed it appears to be empty.

3. Right click the constant and select '\'-Codes Display.

Here you go!

 

Please note that spreadsheet is commonly understood as a file which delimits columns with a tabulator. Using a comma would result in a "comma seperated value" file (csv). As far as i know, csv is mainly used in the US where "normal" spreadsheets are more common to the rest of the world.....

 

hope this helps,

Norbert 

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 9
(3,679 Views)

Norbert B wrote:

Guillaume,

 

what version of LV are you using?

Nevertheless, i think that you are incorrect about this regardless of the LV version you are using. Please do the following:

1. Create a new VI, drop the "Write to spreadsheet file.vi". The Context Help states that \t is the default value for the delimiter.

2. Create a constant for the delimiter. Indeed it appears to be empty.

3. Right click the constant and select '\'-Codes Display.

Here you go!


Alternatively, just try writing data.  When you open the file, the values are tab delimited.

--
Tim Elsey
Certified LabVIEW Architect
0 Kudos
Message 3 of 9
(3,673 Views)

Nay. Using Labview Professional Development 8.6 (.0 I suppose), and following the proposed procedure, the string constant is hopelessly empty. Definitely a bug I think.

 

Thanks,

 

Guillaume.

0 Kudos
Message 4 of 9
(3,659 Views)

GuillaumeL wrote:

Nay. Using Labview Professional Development 8.6 (.0 I suppose), and following the proposed procedure, the string constant is hopelessly empty. Definitely a bug I think.

 

Thanks,

 

Guillaume.


 

 

Could someone with LV 8.6 verify the above?

 

If this can not be confirmed there is the possiblity that your version got saved with bad default values.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 5 of 9
(3,654 Views)

I use version 8.6.1f1 and have no trouble.  I used to use 8.6 and Write to Spreadsheet a lot, without problem.

 

I just checked on another computer in my office with 8.6.  \t is the default.

Message Edited by elset191 on 11-04-2009 11:04 AM
--
Tim Elsey
Certified LabVIEW Architect
Message 6 of 9
(3,647 Views)
Solution
Accepted by GuillaumeL

elset191 wrote:
I use version 8.6.1f1 and have no trouble.  I used to use 8.6 and Write to Spreadsheet a lot, without problem.

 

Thank you Tim!

 

Guillaume,

 

You can either open the FP of the Write to... set it to \t (slash code dispaly) and then right click and choose data ... make current values default,

OR

Do a repair on your LV install.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 7 of 9
(3,643 Views)

Ok. Weird it's only me, but as long as I know it, its no big deal.

 

Thanks everyone,

 

G.

0 Kudos
Message 8 of 9
(3,637 Views)

GuillaumeL wrote:

Ok. Weird it's only me, but as long as I know it, its no big deal.

 

Thanks everyone,

 

G.


 

Actually it is not too weird. Accidental changes to VIs in VI.lib have been around since I have been wiring (virtually, not physically, DOS wasn't even a twinkle in Bill Gates' eye when I started physical wiring Smiley Wink )

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 9 of 9
(3,631 Views)