|With all the stuff I've read, this appears to be the Windows standard.|
Correct! POSIX uses just a new line (\n). Apple chose to use just a carriage return (\r), but then they made OS X, which is based off of FreeBSD. So now they use just a \n. Windows uses both (\r\n) because it copied MS-DOS, which used both. MS-DOS used both because it copied CP/M, which used both. CP/M used both because the teletype typically used with CP/M required both. [As an aside, CP/M used the forward slash (/) for command line switches. This is why Window's path separator is the back slash (\).] And that's your history lesson for the day.
If you're using a Windows program, and it doesn't support \r\n for new lines, it is a buggy program and you should complain until the vendor/programmer fixes it.
Const filePath = "out.txt" '"A:\directory\leading\to some\file.ext"
Set fso = CreateObject("Scripting.FileSystemObject")
fileText = fso.OpenTextFile(filePath).ReadAll
fso.OpenTextFile(filePath, 2, True).Write Replace(fileText, vbCr, "")
How To Ask Questions The Smart Way