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
--
Regards
Sytze de Boer
Kiss Software
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
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/AANLkTim=-3qYY3HW=b_OwmzmMa+u2Tg3zkGGLb2cELaf@mail.gmail.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.
What is the offending client's os?
Rick Q
quilhotr@gmail.com
On Thu, Mar 24, 2011 at 10:25 PM, Sytze de Boer <sytze.kiss@gmail.com>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
>
>
>
> --
> Regards
> Sytze de Boer
> Kiss Software
>
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
> text/plain (text body -- kept)
> text/html
> ---
>
[excessive quoting removed by server]
_______________________________________________
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/AANLkTikWrpJmN6XbM-bECgFuGNh5LLaubTUxj9=00-15@mail.gmail.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.
XP Pro
On Fri, Mar 25, 2011 at 3:38 PM, Richard Quilhot <quilhotr@gmail.com> wrote:
> What is the offending client's os?
>
> Rick Q
> quilhotr@gmail.com
>
>
>
>
> On Thu, Mar 24, 2011 at 10:25 PM, Sytze de Boer <sytze.kiss@gmail.com
> >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
> >
> >
> >
> > --
> > Regards
> > Sytze de Boer
> > Kiss Software
> >
> >
> > --- StripMime Report -- processed MIME parts ---
> > multipart/alternative
> > text/plain (text body -- kept)
> > text/html
> > ---
> >
[excessive quoting removed by server]
_______________________________________________
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/AANLkTi=CxEGxu6q1OfFKK55qsfBj9_BFjja3VWZPkf-B@mail.gmail.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.
Only thing I can think of is to look at the localization settings within XP.
Maybe they have set an unusual codepage or something.
Rick Q
quilhotr@gmail.com
On Thu, Mar 24, 2011 at 10:56 PM, Sytze de Boer <sytze.kiss@gmail.com>wrote:
> XP Pro
>
> On Fri, Mar 25, 2011 at 3:38 PM, Richard Quilhot <quilhotr@gmail.com>
> wrote:
>
> > What is the offending client's os?
> >
> > Rick Q
> > quilhotr@gmail.com
> >
> >
> >
> >
> > On Thu, Mar 24, 2011 at 10:25 PM, Sytze de Boer <sytze.kiss@gmail.com
> > >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
> > >
> > >
> > >
> > > --
> > > Regards
> > > Sytze de Boer
> > > Kiss Software
> > >
> > >
> > > --- StripMime Report -- processed MIME parts ---
> > > multipart/alternative
> > > text/plain (text body -- kept)
> > > text/html
> > > ---
> > >
[excessive quoting removed by server]
_______________________________________________
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/AANLkTin8enbLzwKWoDH9c-mRuJGugnL0510oCvCTdOiJ@mail.gmail.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.
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.
I agree with Paul. Sounds like you're getting just LF inside your DO WHILE loop. Here's another idea for getting your results. Untested, of course... <g>
sele dcdetail
scan for len(alltrim(dcdets))>0
m.Text2Export= m.Text2Export+iif(not(empty(m.Text2Export),chr(13)+chr(10),[])+ m.Text2Export
endscan
if not empty(m.Text2Export)
m.Text2Export= m.Text2Export+CHR(13)+CHR(10)
strtofile(m.Text2Export,[DCSCHED.TXT])
endif
--
rk
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Paul McNett
Sent: Friday, March 25, 2011 12:11 AM
To: profoxtech@leafe.com
Subject: Re: TXT file with vfp9
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.
_______________________________________________
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/DF1EEF11E586A64FB54A97F22A8BD04419225925C6@ACKBWDDQH1.artfact.local
** 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.
Guys, thank you for your input.
However, whatever the problem is, why is this only occurring at one site and
not at 500 others.
That is why I think it is system or printer related, rather than anything in
my code
S
On Sat, Mar 26, 2011 at 12:19 AM, Richard Kaye <RKaye@artfact.com> wrote:
> I agree with Paul. Sounds like you're getting just LF inside your DO WHILE
> loop. Here's another idea for getting your results. Untested, of course...
> <g>
>
> sele dcdetail
> scan for len(alltrim(dcdets))>0
> m.Text2Export=
> m.Text2Export+iif(not(empty(m.Text2Export),chr(13)+chr(10),[])+
> m.Text2Export
> endscan
> if not empty(m.Text2Export)
> m.Text2Export= m.Text2Export+CHR(13)+CHR(10)
> strtofile(m.Text2Export,[DCSCHED.TXT])
> endif
>
> --
> rk
>
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
> On Behalf Of Paul McNett
> Sent: Friday, March 25, 2011 12:11 AM
> To: profoxtech@leafe.com
> Subject: Re: TXT file with vfp9
>
> 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.
>
>
[excessive quoting removed by server]
_______________________________________________
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/AANLkTinFogdiomYa2SB4SMoUECcTwPUtYVgrAwuMhLGO@mail.gmail.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.
I don't think it's in your code...I think it's a code-page problem which
is a Windows issue.
Mike
> Guys, thank you for your input.
> However, whatever the problem is, why is this only occurring at one site and
> not at 500 others.
> That is why I think it is system or printer related, rather than anything in
> my code
>
> S
>
>
>
> On Sat, Mar 26, 2011 at 12:19 AM, Richard Kaye<RKaye@artfact.com> wrote:
>
>> I agree with Paul. Sounds like you're getting just LF inside your DO WHILE
>> loop. Here's another idea for getting your results. Untested, of course...
>> <g>
>>
>> sele dcdetail
>> scan for len(alltrim(dcdets))>0
>> m.Text2Export=
>> m.Text2Export+iif(not(empty(m.Text2Export),chr(13)+chr(10),[])+
>> m.Text2Export
>> endscan
>> if not empty(m.Text2Export)
>> m.Text2Export= m.Text2Export+CHR(13)+CHR(10)
>> strtofile(m.Text2Export,[DCSCHED.TXT])
>> endif
>>
>> --
>> rk
>>
>> -----Original Message-----
>> From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
>> On Behalf Of Paul McNett
>> Sent: Friday, March 25, 2011 12:11 AM
>> To: profoxtech@leafe.com
>> Subject: Re: TXT file with vfp9
>>
>> 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.
>>
[excessive quoting removed by server]
_______________________________________________
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/4D8D1466.50809@ggisoft.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.
Have to checked the version of the printer driver on the PC in question?
You might want to look into the StrToFile() command as a way to bypass using
the print rountine.
Rick Q
quilhotr@gmail.com
On Fri, Mar 25, 2011 at 6:10 PM, Sytze de Boer <sytze.kiss@gmail.com> wrote:
> Guys, thank you for your input.
> However, whatever the problem is, why is this only occurring at one site
> and
> not at 500 others.
> That is why I think it is system or printer related, rather than anything
> in
> my code
>
> S
>
>
>
> On Sat, Mar 26, 2011 at 12:19 AM, Richard Kaye <RKaye@artfact.com> wrote:
>
> > I agree with Paul. Sounds like you're getting just LF inside your DO
> WHILE
> > loop. Here's another idea for getting your results. Untested, of
> course...
> > <g>
> >
> > sele dcdetail
> > scan for len(alltrim(dcdets))>0
> > m.Text2Export=
> > m.Text2Export+iif(not(empty(m.Text2Export),chr(13)+chr(10),[])+
> > m.Text2Export
> > endscan
> > if not empty(m.Text2Export)
> > m.Text2Export= m.Text2Export+CHR(13)+CHR(10)
> > strtofile(m.Text2Export,[DCSCHED.TXT])
> > endif
> >
> > --
> > rk
> >
> > -----Original Message-----
> > From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
> > On Behalf Of Paul McNett
> > Sent: Friday, March 25, 2011 12:11 AM
> > To: profoxtech@leafe.com
> > Subject: Re: TXT file with vfp9
> >
> > 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.
> >
> >
[excessive quoting removed by server]
_______________________________________________
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/AANLkTinzWDtX53gM3sKsHkcN2Y+SGbKreb1QPpnG-D64@mail.gmail.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.
> -----Original Message-----
> From: profoxtech-bounces@leafe.com
[mailto:profoxtech-bounces@leafe.com]
> On Behalf Of Sytze de Boer
> Sent: Friday, March 25, 2011 3:11 PM
> To: profoxtech@leafe.com
> Subject: Re: TXT file with vfp9
>
> Guys, thank you for your input.
> However, whatever the problem is, why is this only occurring at one
site
> and
> not at 500 others.
> That is why I think it is system or printer related, rather than
anything
> in
> my code
>
If this machine is at a bank, like you said - check printer drivers.
Maybe at one time (or now has been changed to) interfacing w/ a cash
machine or some such special purpose device and the driver (or lack of
one) is messing things up.
I have a buddy that works for a credit union and something like this
drove their entire dept NUTS for 6 months...
Thanks,
Matthew Jarvis || Business Systems Analyst
IT Department
McKenzie-Willamette Medical Center
1460 G Street, Springfield, OR 97477 || Ph: 541-744-6092 || Fax:
541-744-6145
--------------------------------------------------------------------------
Disclaimer: This electronic message may contain information that is
Proprietary, Confidential, or legally privileged or protected. It
is intended only for the use of the individual(s) and entity named
in the message. If you are not an intended recipient of this
message, please notify the sender immediately and delete the
material from your computer. Do not deliver, distribute or copy
this message and do not disclose its contents or take any action in
reliance on the information it contains.
_______________________________________________
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/69F310C05DD83C48A84BA3769CE1ECF804727EE5@TNTRIEXEVS02.triadhospitals.net
** 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.