printer file "name" - problem

Kenneth Brody kenbrody at bestweb.net
Thu Mar 17 13:53:38 PST 2005


Quoting Dennis Malen (Thu, 17 Mar 2005 16:09:26 -0500):
[...]
> I will go back and try it again but the two problems I was initially
> having with this code are:
>
> 1. It would not over ride the defined printer in the report format. I
> solved
> that by copying over the report and not defining a printer (shouldn't
> have
> to do that);

If the PRINTER commands in your processing are not overriding the
printer defined on the output format, then the only thing I can
think of is that you're not actually executing the PRINTER commands.

Have you tried the simple MESGBOX test that I suggested yesterday?

> 2. When I copied the report over so there was no interference with any
> defined printer (since there was none) the file created was composed of
> each
> record being written and then adding 63 blank lines (definition of the
> page
> length was 64) and wrote the next page in a similar fashion. Pulling 93
> records creating 93 pages scrolling through the screen. When I defined
> the
> length of the page as 1 (as opposed to 64), it then printed correctly on
> the
> screen.

If the page length is set to 64 lines, I would expect 64 lines per page.
Are you generating a page break somehow between each record?

[...]

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com


More information about the Filepro-list mailing list