printing problem

[Martijn]

In my application I want to print a label (not a object , but a paperone).
The problem is that the labels ar not the same size as a standard A4 format,
they are
smaller, about 152mm high.

When i give the following command, the printer prints the text and then goes
to the
next page. The problem is that the labels are smaller then the A4 format
that the printer
is using, and I don't now who to set this (or what propety) to mek the
printer go to the
next page after 152mm instead off 298mm (A4).

Printer.Print "hello world
Printer.EndDoc

Maybe someone can give me some advise.

Thanks from Holland
Martijn.

[Raoul Watson]

"Martijn" <in**@NSdiscowinkel.nl> wrote in message
news:3f***********************@news.versatel.net.. .

In my application I want to print a label (not a object , but a paperone).
The problem is that the labels ar not the same size as a standard A4 format, they are
smaller, about 152mm high.

When i give the following command, the printer prints the text and then goes to the
next page. The problem is that the labels are smaller then the A4 format
that the printer
is using, and I don't now who to set this (or what propety) to mek the
printer go to the
next page after 152mm instead off 298mm (A4).

Printer.Print "hello world
Printer.EndDoc

Maybe someone can give me some advise.

Thanks from Holland
Martijn.

Have you explore advancing the paper manually (i.e. by issuing print
statements). The .EndDoc will create problem because that issues the chr) or
Form Feed. My suggestion is to manually issue rint statements to include one
that will "page oiverflow" to the next page and continue fro there. When the
job is completed (all labels printed), at that timme issue the EndDoc.

Beste wensen van New York.

[J French]

On Sat, 02 Aug 2003 12:29:50 GMT, "Raoul Watson"
<Wa*****@IntelligenCIA.com> wrote:
<snip>

Have you explore advancing the paper manually (i.e. by issuing print
statements). The .EndDoc will create problem because that issues the chr) or
Form Feed. My suggestion is to manually issue rint statements to include one
that will "page oiverflow" to the next page and continue fro there. When the
job is completed (all labels printed), at that timme issue the EndDoc.

I would not fancy using that through the VB Printer Object

It knows all about the height of a page

That used to be a good way of printing to dot matrix style printers
under DOS

[Raoul Watson]

"J French" <er*****@nowhere.com> wrote in message
news:3f***************@news.btclick.com...

On Sat, 02 Aug 2003 12:29:50 GMT, "Raoul Watson"
<Wa*****@IntelligenCIA.com> wrote:
<snip> It knows all about the height of a page

That info is whatever is returned by the printer properties. You can fool
the system by saying you have a 50 feet long paper. It does not care.

[J French]

On Sat, 02 Aug 2003 13:30:34 GMT, "Raoul Watson"
<Wa*****@IntelligenCIA.com> wrote:

"J French" <er*****@nowhere.com> wrote in message
news:3f***************@news.btclick.com...

On Sat, 02 Aug 2003 12:29:50 GMT, "Raoul Watson"
<Wa*****@IntelligenCIA.com> wrote:
<snip>

It knows all about the height of a page

That info is whatever is returned by the printer properties. You can fool
the system by saying you have a 50 feet long paper. It does not care.

Could that not be a bit nasty ?

The Printer Object creates a memory image of the page ...

[J French]

BTW, as I pointed out to the OP in anothe VB NG
- all he needs to do is to jigger the Height property of the Printer
Object to set the page height to whatever he wants

On Sun, 3 Aug 2003 08:22:28 +0000 (UTC), er*****@nowhere.com (J
French) wrote:

On Sat, 02 Aug 2003 13:30:34 GMT, "Raoul Watson"
<Wa*****@IntelligenCIA.com> wrote:

"J French" <er*****@nowhere.com> wrote in message
news:3f***************@news.btclick.com...

On Sat, 02 Aug 2003 12:29:50 GMT, "Raoul Watson"
<Wa*****@IntelligenCIA.com> wrote:
<snip>

It knows all about the height of a page

That info is whatever is returned by the printer properties. You can fool
the system by saying you have a 50 feet long paper. It does not care.

Could that not be a bit nasty ?

The Printer Object creates a memory image of the page ...