VsiFax and filePro -- frustration!

[Steve Parker]

-----Original Message-----
From: Jim Asman [mailto:jlasman at telus.net] 
Sent: Saturday, August 28, 2010 4:35 AM
To: sparker at abccompuserve.com
Subject: Re: VsiFax and filePro -- frustration!

--------------- Original Message ---------------
At 12:44A Sat Aug 28 2010, Steve Parker wrote:
> 
> The selected records are processed one by one through the report, hitting
an
> "end" statement at the end of each record. When the customer number
changes,
> a GOSUB statement sends the FAX. I've even gotten clever enough that the
> file names are unique with the "customer number" { "-" { date (without
> slashes) so the failed FAXes can be easily tracked and processed manually.
> 
> At this point I'm looking for some ideas. I'm pretty lost on this right
now,
> and pretty burned out as well!! LOL!
> 
> Any ideas? In particular, can anyone shed light on "block" #1 with the
extra
> line feeds, or with "block" #2 some insight on the PRINTER FILE command
that
> will help me understand what I am doing wrong?


Steve,

Your extra CR/LF's are likely from filepro where the "# lines to print" is
less than "# lines per page". Filepro does the padding after the record is
processed. You may need and appropriate PCL page formatting command to
keep it all in synch between filepro and vsifax.

Before your PRINTER FILE command, issue a PRINTER RESET and see if you
get the entire record. 


Jim 
--
jlasman at telus.net                      Spectra Colour Services Ltd.
Jim Asman                              10221 144a Street            
Phone: (604)584-0977                   Surrey, BC  V3R 3P7   CANADA

 Cell: (604)619-0977                   www.spectracolorservices.com
---------------

Jim,

Thank you for your input, but here's what I have in response.

Using my original programming with the "PRINT" command, the first page
always comes out as 64 lines, which is what VsiFax seems to like. The next
record prints with 12 lines at the top. I have even tried to remove those
lines in a number of ways: 1) using the system command to "rm" the file (the
process prints no more!) 2) using the system command to "cat" the output
file to "null", 3) using the system command to "cat" an empty file (or a
file with 1 ^M in it over top of the last output file. 

None of this has worked. I think I even tried the "cat" command just prior
to "printing" a new record and right after "faxing" a record. Same story.

As for the PRINTER FILE command, I have tried PRINTER FLUSH and PRINTER
RESET to try to get all of the information "pushed" out. Part of the problem
seems to be that the file is being created in pieces, as a given statement
is the assembly of multiple records. The PRINT command seems to "PRINT" just
what is processed at the "END" command, so the first one encountered prints
the "header" with the first record, then each succeeding one adds just one
line to the file, until the last record is hit with the @WBR1 is hit. This
forces the processing to go to this point where the "totals" are calculated,
printed, and the end of the record is added. 

Then the processes goes into a routine that "faxes" the record.

Here is where my problem is. No matter what I do, I seem to get the 12 lines
at the top of the next record.

But each PRINTER FILE command creates a whole 64 line page, be it the
header, additional records, or the end.


Steve