TDMS Write cannot accept datatype - what's going on here then?

[Thoric]

Why should the Transpose function cause an issue like this then?

This VI was sent to me by someone, so don't ask what I'm trying to do because I'm not trying to do anything, but I am curious about the broken wire, and why converting the datatype from [SGL] to [DBL] and back to [SGL] keeps LV happy. 

[Darin.K]

Reminded me of this:

http://forums.ni.com/t5/LabVIEW/Weird-network-stream-broken-wire/td-p/2824640

And I would wager that once again 'Always Copy' would fix your little problem

[Thoric]

Bingo

[Hooovahh]

Before seeing your latest post I was going to suggest always copy.  Lets add it to the list.

http://lavag.org/topic/16336-cannot-register-event-for-array-of-references-on-a-conpane-code-include...

http://lavag.org/topic/15069-lv2010-weirdness/

http://lavag.org/topic/16973-bug-when-using-get-waveform-attribute-in-subvi/

http://lavag.org/topic/17833-class-data-inside-dvr-being-deleted/

http://forums.ni.com/t5/LabVIEW/bug-in-cluster-to-array-in-for-loop-with-non-indexed-output/m-p/8531...

http://forums.ni.com/t5/LabVIEW/Unxepected-behaviour-with-clusters-inside-of-while-loop-with/m-p/793...

http://forums.ni.com/t5/LabVIEW/WARNING-TDMS-memory-leak-in-LV-2010/td-p/1874575/page/2

http://forums.ni.com/t5/LabVIEW/EXE-Won-t-Build/m-p/2898868

https://forums.ni.com/t5/LabVIEW/TDMS-Write-cannot-accept-datatype-what-s-going-on-here-then/m-p/293...

One of those is where a nasty memory leak issue with transpose, then a normal TDMS write.  At least here it breaks the wire so that memory leak isn't possible.