home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!uknet!mcsun!sunic!seunet!enea!tope
- From: tope@enea.se (Tommy Petersson)
- Newsgroups: comp.os.ms-windows.programmer.misc
- Subject: VB, Windows and printing
- Keywords: VB, printing
- Message-ID: <1992Dec21.132516.21464@enea.se>
- Date: 21 Dec 92 13:25:16 GMT
- Reply-To: tope@enea.se (Tommy Petersson)
- Organization: Enea Data AB, Sweden
- Lines: 30
- Uucp-Path: mcvax!kth!sunic!enea.se!tope
-
- We are doing a small application in Visual Basic 2.0 Pro, to run on
- Windows 3.1 clients in a Lan Manager Network.
-
- Reports from our application need to be printed in landscape orientation
- on a Nec PostScript laser printer. This is easy by selecting landscape
- mode in Control Panel/Printer. However, everything else the users print
- should be portrait, and they of course don't want to manually change the
- preferences all the time.
-
- There seem to be two choices here:
-
- Let Visual Basic still use the "Printer" object, (which only works on
- the default printer). For every report in our application, set the printer
- to landscape, and reset it afterwards.
-
- Forget about the Printer object, stuff the default printer, use Windows
- calls to get/change device context and don't mess with the default printer
- whatsoever.
-
- Which is best? Or is there a better way of doing it?
-
- In "your best solution" - how do you do it? (I have looked only briefly
- on the GetDeviceContext, ExtDeviceMode, Escape and other calls)
-
- Pro's and con's?
-
- --
- =============================================================================
- Tommy Petersson tope@enea.se Enea Data AB, Sweden
- =============================================================================
-