12-12-2007 07:48 PM
12-12-2007 09:14 PM - edited 12-12-2007 09:19 PM
I think your problem is that you are using a comma has your decimal separator rather than a decimal point ".".
If you are writing out your various values to a text file and the values are comma delimited, then the commas you are using as a decimal point are being confused as a delimiter rather than being an inherent part of the decimal value. I suggest using the standard of a period as the decimal point (but I'm not sure if Excel would still have a problem if your windows settings are using an international setting of comma). Perhaps wrapping the text part of your time and date in quotes so Excel will import the date and time as a single entity rather than 2-3 entities because of the comma embedded in it. But that doesn't explain why Excel would be crashing.
It sounds like you are already handling the 1/1/1904 in Labview vs. 1/1/1900 in Excel base date okay as well as seconds in LV vs. days in Excel..
(By the way, I think 0.5 in Excel is 12:00:00 PM not 12:00:00 AM)
Which version of Excel are you using? Most versions of Excel only got to 65,000 + rows. Only the latest version goes up to 1 million or something like that. Could that be the source of your crash?
Edit: Perhaps one other possibility would be to use another character as a delimiter such as TAB or any other character that doesn't usually show up in data files such as pipe | or tilde ~
12-12-2007 11:18 PM
12-13-2007 11:20 AM
12-13-2007 11:25 AM - edited 12-13-2007 11:27 AM
12-13-2007 12:17 PM
Write to spreadsheet file in File I/O pallette. But it's possible it did not exist until more recent versions of Labview.
It basically takes the array and puts each element together into a single string using delimiters and end of file characters as necessary and writes it out using the text file I/O functions.
Also look at the array to spreadsheet string in the String pallette.
12-16-2007 01:13 AM - edited 12-16-2007 01:14 AM
12-16-2007 01:41 PM
12-16-2007 01:56 PM
12-16-2007 02:00 PM