Excel treatment of Char(11)

Copper Contributor

I'm hoping this is not off topic for this forum, but I really don't know where else to go. 

I have for several years used a way of 'generating' a risk register in Excel by dumping data into a simple table and using calculations to generate the data from the 'dump tab'.

Where there line feed in my data there is a Char(11) character [Vertical Tab] that is stored inline in cell contents. 

Now when i dump to the excel dump tab it sees each Char(11) as a line feed and drops the data down into another row! I don't want that!


Why is this happening ? is there a way that I can direct excel's interpretation of this character?



4 Replies
I think https://techcommunity.microsoft.com/t5/excel/bd-p/ExcelGeneral could be a better place to ask this question.


Hello! You've posted your question in the Tech Community Discussion space, which is intended for discussion around the Tech Community website itself, not product questions. I'm moving your question to the Excel space (@Harm_Veenstra was correct there)- please post Excel questions here in the future.  


Thanks Harm, but since finding the answer in consultation with a Microsoft tech support person, the question morphs into one of typical Microsoft disregard for it's customer base. So, back to appropriate for this forum, I think.

In moving from a very old laptop (Core i3) running Windows 10 and on to a laptop running Windows 11 it seems that Microsoft kindly upgraded its Notepad.exe to a lovely new version that interprets the Char(11) character as a Carriage Return (Char(13)). The solution was to turn this gift off and revert to the classic Notepad.exe.

Thank you Microsoft for causing me a whole **bleep** morning of dedication the work around for this 'upgrade'. If Microsoft developers actually used their operating system in a real world environment outside of their ivory tower with perfect internet access and unlimited time for laptop management, they might see the inadequacy of their product(s).


Just read this again. Got it. Thanks for moving my question.
But now the answer, as mentioned to Harm Veenstra, maybe better to move it to 'Let's all switch to UNIX' forum. :)
Thanks again.