If you really need them to be separate jobs, and make sure no other jobs slip in between, the best way might to be to temporarily un-share the printer for all other users.

In your system32 directory you will find a bunch of prn*.vbs scripts that will give you some ideas about how to manage printers programmatically. The user in whose context the scripts (or equivalent commands) run has to have printer management permissions, of course.

One approach that would probably make it easiest to script (or, failing that, for somebody to perform from a UI interface) would be something like this:

* -- have two printer setups for this printer

* -- give only the user(s) in whose context this job runs permissions for one of them

* -- give everybody else permissions for the other

* -- at the start of the job, unshare printer setup #2

* -- at the conclusion, re-share it.

Just a thought...


>L<