Is there any way that VBScript (or another method) on a Windows box under Windows 2003 FMSA8 can capture a problem at our (networked) printer. Microsoft pops up with printer error messages all the time. We have printings that are critical. If we have a problem, sometimes we need to stop a process until the proper documents are printed.

I want my script to know (not only from User verification) that everything went smoothly. They read the message, "Did bla-bla print correctly?" and, no matter how big I make the message; no matter how I word it, they sometimes click "YES" when it didn't. Very very bad. Can I make script pause until it DOESN'T receive a print error within a certain number of seconds at least?

Ideas appreciated ...

LaRetta

Hi L.

Not an easy task... VBscript can capture a printer error when it generated a print job itself. But monitoring a print job from an external (FM) source is not trivial.

There are VBscripts that can work with the printer queue and printer status. And then there is the real VB that can monitor for popup messages and read those.

But the heads-up I wanted to give you here is that there is not an quick and easy solution for this. It would involve some heavy duty coding.

Hello there, Wim!

Okay, well I guess if they get sent to the Principle's office then they're respect messages a bit more. I dislike strong tactics so I'll build in even more protections. Maybe I'll make my messages flash in neon with the word DANGER. ROFLMAO!

LaRetta

Let me know if you want me to send them a stern message :)

There are two new people would could use a bit of rough talk, for sure, Wim. They're the ones who, when the printer jams, run up and hit cancel even if it's someone else's job (which the printer is tracking and would re-print those pages anyway). I guess no print-error trapping would have helped anyway - I was just grabbing for all possibilities.

L

They're the ones who, when the printer jams, run up and hit cancel even if it's someone else's job

LOL!