Rog, > It doesn't work very well in a production environment where the report(s) > are run MANY times per day. Like with Sales Orders or Packing Lists > warehouse pick lists or Invoices, especially when the printers are networked > and/or remote.
My application runs in a similar environment -- I believe you can work around all these issues to a large extent. I already control margins separately for each report based on duplicating a generic printer setup so that's not an issue. Also, you can individually change any read/write property of the printersetup object except the setupstring -- which is only useful for storing setting between application runs. > To have to select and set up the printer every time you printed a report, > (margins, printer, input tray, output tray, orientation, duplex, copies) > would be... No, not every time you print, you only have to do a printer dialog and/or page setup once per application run. I think this not so much a burden as things often change between app runs that may mean a printer is no longer available or on line. Make your initial printersetup and graphics classes module globals, and they'll be there for the rest of the application run. Just nil g at the end of each printer run and keep ps populated for the next print job. > Well I just don't want to be in phone range for that one. Does this help at all? Keith DeLong _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
