On 3/24/11 7:25 PM, Sytze de Boer wrote:

> In one of my systems, I create a TXT file which is then imported by banking

> software

> I've never had a problem with this, until today

> The code is 10 years old or more.

>

> With this one client, I end up with one continuous line in the text file

> With everyone else, I end up with a neat txt file with multiple lines

> I can't figure why this simple code behaves differently with this one client

>

> I'm inclined to add a simple chr(13) where it says

> @l,0 say alltrim(dcdets)

> but I don't want to screw it up where this has never been an issue

>

> Does anyone wish to comment?

>

> set devic to print

> set printer to DCSCHED.TXT

> @0,0 say ""

> sele dcdetail

> delete for len(alltrim(dcdets))=0

> go top

> l=0

> do while !eof()

> @l,0 say alltrim(dcdets)

> l=l+1

> skip

> enddo

> @prow(),pcol() say chr(13)+chr(10)

> set printer to

> set devic to scree

Look at the output in a hexeditor and make sure you are getting CRLF's and not bare

CR's or LF's. If this client is running the software on Linux using Wine, they could

be getting bare LF's which is normal on that platform. There could be other reasons, too.

Paul

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4D8C15C8.8000603@ulmcnett.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.