markphsd,
Yes you can always use DevMode. I, unfortunately, have to use it quite a bit. Aside from understanding all the different code structures for the settings, much of the documentation provided by MS is not quite correct and not every printer driver follows all the rules all the time.
The biggest drawback of using DevMode on the report itself is that you can't change a setting without opening the report in design view. If you're in design view, your mdb is multiuser, has lots of reports and is on the network, you can't have more than one user running a specific report at a time.
Even in Access XP the provided routines don't work the way they should. Many of the bits in the DevMode after the first section, for things like stapling & punching, get dropped, so you can't change them at all.
Before Win 2000 we had to have multiple copies of most every report in the mdb, each with different printer settings, or copy a report and change the settings on that copy, deleting it when done. Now we try to set the reports to default and change the settings the users default printer to match what we want in the report - instead of changing them on the report.
We have about 50 different printers, mostly Canons and HPs, on 3 different servers at various sites. Even printers of the same model don't always use the same driver; just like code, they have version releases. Some printers run PCL, others Postscript, some both.
In theory, every printer uses the first section of the DevMode (listed in the code examples) for the same purposes. For example, duplexing has a flag and specific long value address. Canon IR8500 PCL drivers use this address but the Canon IR8500 Postscript does not. It's the same physical printer but it can use different drivers.