printing to windows spooler - width of doc problem

[Dennis Malen]

Bob,

Your good!!

I was playing around with the various codes that were in my HP-4+ 
definitions. The last one I used was $ib @s1c. This was in my definitions 
from day one in filePro.

When I spoke to Jim Asman he suggested that I use $1b &s1C. I tried this one 
first and it did not work so I looked in the definitions for something else 
to use and I found the one above. I tried it and it did not work. The blank 
spaces between the "s" and "1" and between the "1" and "c" are not in my 
definition. It has no spaces. In any event, neither code worked.

As far as the linefeed at the 80th character, I looked in our report format 
and found no codes that were imbedded. Is it possible that the windows 
spooler  placed a line feed automatically? The width of my page in filePro 
is 132.

As far as capturing the file on the server that is how my prior attachment 
that you viewed was created.

Again I'm not trying to be stubborn about using the alternative by  printing 
to an IP address. We do that all the time. We need to use the spooler 
approach in order to have files scanned in automatically which would save us 
hours of time during the day, every day. Right now we are using bar codes 
(provided by Jim Asman) which works great. We must go though the windows 
spooler in order to access third party vendor to allow that function to 
work.

Regards,

Dennis Malen
516.479.5912
----- Original Message ----- 
From: "Bob Rasmussen" <ras at anzio.com>
To: "Dennis Malen" <dmalen at malen.com>
Cc: <filepro-list at lists.celestial.com>
Sent: Tuesday, April 05, 2005 10:17 PM
Subject: Re: printing to windows spooler - width of doc problem


> On Tue, 5 Apr 2005, Dennis Malen wrote:
>
>> Bob,
>>
>> Attached is the file showing the codes that were captured. Jim Asman also
>> suggested the same approach.
>
> The data file shows a linefeed (hex 0A) 80 characters into the header
> line; that is, between the "a" and the "n" of "Exchange". So it's not the
> physical printer that's breaking the lines.
>
> Next step: capture the file on the server and see if the linefeed is in it
> there.
>
> Also, you have an erroneous escape sequence:
>   Esc @ s 1 c <space>
>
> This is wrong on several counts:
>
> 1) There is not an "@" in any PCL sequence. Did you mean "&"?
>
> 2) A sequence must end with an uppercase letter.
>
> 3) The space is probably not supposed to be there.
>
> Regards,
> ....Bob Rasmussen,   President,   Rasmussen Software, Inc.
>
> personal e-mail: ras at anzio.com
> company e-mail: rsi at anzio.com
>          voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
>            fax: (US) 503-624-0760
>            web: http://www.anzio.com
>
>
>