Thanks Mark for your solution. I'll imediately look into it.
I do have direct access to the server in question.

By the way, thats 300 documents per week! While it would help the
unemployement rate  to hire a temp to print the 300 documents, I would
rather just give my user a PRINT button that prints everything in the
server directory.

Thanks again. As always you have been very helpful!

Steve

Create a small thick client application (let's call it the print
manager) that gets installed on the dealers machine's. This can be a
simple executable that need not run as a service or even in the task
tray. Once all of the documents have been generated (as separate
documents on the server) and saved to the appropriate location on the
server (preferably in the database) a special document should be
downloaded to the client (called a manifest) that contains a list of
all the files (or file IDs) that need to be printed as well as their
print options. The manifest should have a unique extension that is
recognized and associated with the print manager such that when the
file is opened, the print manager automatically launches. The print
manager will download each document listed in the manifest and
automatically print it. Because the print manager runs as a thick
client, it can directly communicate with the printer, setting the
approprate page size, orientation and duplex settings. Alternatively,
the manifest file could contain only the list of documents and the
print options could be sent as meta-data along with the document.
Prefered method for communicating with the server