i was already thinking was it now only the cariage return or the linefeed
??? :-) just checked some verry old source ( VB 5 / 6 ) and yes Phil you
beated me before i could correct it
well it is so long ago that i had to write files to the system for
exchanging data with third party software
and yes we did write those files to Linux \ Unix file shares and they worked
perfectly ( without any strange conversions or what so ever )
by the way Phil W is that 'the' Phil Weber from the good old days on
freevbcode.com and now Devx ? , if so nice to see you again on the web
Phil
regards
Michel Posseth
"Phill. W" <P.A.Ward@o-p-e-n-.-a-c-.-u-k> wrote in message
news:dg**********@yarrow.open.ac.uk...
"Lyle A. Sieren" <no****@developmentnow.com> wrote in message
news:f3**********************************@msnews.m icrosoft.com...
I tried using the following code but it left me with a line carriage
return in the file (0d0a)
outfilew.Write(group6)
outfilew.Write(Environment.NewLine)
If this is run on a Windows box, it will use vbCrLf (0d0a) for a line
break. Unix only wants vbLf (0a). Change your code to
outfilew.Write(group6)
outfilew.Write(vbLf)
(or, better still)
outfilew.Write(group6 & vbLf)
HTH,
Phill W.