By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,701 Members | 2,006 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,701 IT Pros & Developers. It's quick & easy.

Check if printer is active

P: n/a
Hi!

Is there any way to check if printer is active in access 2000?

I have a report that is printing (local printer), and before I do
anything more in code, I do want to check if printer is active.

Do I access the windows messaging system or...?

Anybody got a clue?

Me.Name
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
> Is there any way to check if printer is active in access 2000?

I have a report that is printing (local printer), and before I do
anything more in code, I do want to check if printer is active.

Do I access the windows messaging system or...?

Anybody got a clue?

Me.Name


I don't have an answer but I'd be interested in this one as well.

Me.Corrupted
Nov 13 '05 #2

P: n/a

"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:vu********************************@4ax.com...
On 2 Feb 2005 23:41:49 -0800, ge***********@hotmail.com (Geir
Baardsen) wrote:
Is there any way to check if printer is active in access 2000?
I have a report that is printing (local printer), and before I do
anything more in code, I do want to check if printer is active.
Do I access the windows messaging system or...?
Anybody got a clue?


Printers do funny things like "jam", run out of toner, print the wrong
way, print with lines on them, and even lose printing jobs that makes
any automated methods for determining that a job has "finished" a
exercise in futility.

Arvin Miller (if memory serves) once posted a message saying that to
make sure a printing process completed successfully, he printed out an
extra page with a random number on it, and asked the user to type it
in. If what the user types in doesn't match, the job hasn't
completed. I've used that method a couple of times and it works
great, although it is a manual method.

It's also the only one you can completely rely on!
--
A Person's Language Is An Index Of His Mind.


------

Is there anyway to make the random number invisible on the print preview.
Some users may want to save time by previewing the last page to enter the
random number into the system before retrieving the output.
Nov 13 '05 #3

P: n/a

"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:lv********************************@4ax.com...
On Thu, 3 Feb 2005 10:17:46 -0600, "paii, Ron" <pa**@packairinc.com>
wrote:
"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:vu********************************@4ax.com.. .
On 2 Feb 2005 23:41:49 -0800, ge***********@hotmail.com (Geir
Baardsen) wrote:
>Is there any way to check if printer is active in access 2000?
>I have a report that is printing (local printer), and before I do
>anything more in code, I do want to check if printer is active.
>Do I access the windows messaging system or...?
>Anybody got a clue? Printers do funny things like "jam", run out of toner, print the wrong
way, print with lines on them, and even lose printing jobs that makes
any automated methods for determining that a job has "finished" a
exercise in futility.
Arvin Miller (if memory serves) once posted a message saying that to
make sure a printing process completed successfully, he printed out an
extra page with a random number on it, and asked the user to type it
in. If what the user types in doesn't match, the job hasn't
completed. I've used that method a couple of times and it works
great, although it is a manual method.
It's also the only one you can completely rely on!

Is there anyway to make the random number invisible on the print preview.
Some users may want to save time by previewing the last page to enter the
random number into the system before retrieving the output.

I can't find a database I've done this in right now... I know I have
them, I just can't find them. (They're backed up on CD, and I'm
really too tired to look through them. Three 20 hour days in a row
has left me fairly wiped.)

If memory serves however, the Report Activate and Deactivate events
can be used to determine what mode a report is opened in. Neither
event fires when in Print mode, but do for Preview. Use those events
to toggle whether or not the text box with the random number is
populated or not.

There may be some pre-written code at the Access Web for this:
http://www.mvps.org/access/

I also have a half-memory of this, so you'll want to check it out
yourself, but the memory cells are reminding me that if you use the
On_Print event to populate the random number text box, you'll get a
new random number each time the report is "printed" whether it is in
Preview mode or not. So if a user opens the report, scrolls to the
end, then prints the report, the number on the screen won't match the
number on the printed page. Take that with a grain of salt however,
my brain cells are not as young as they used to be.
--
A Bird In The Hand Will Doo Doo On You.

Thank you for your input
I will look into this and Post on this thead if I get something working.

Nov 13 '05 #4

P: n/a

"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:lv********************************@4ax.com...
On Thu, 3 Feb 2005 10:17:46 -0600, "paii, Ron" <pa**@packairinc.com>
wrote:
"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:vu********************************@4ax.com.. .
On 2 Feb 2005 23:41:49 -0800, ge***********@hotmail.com (Geir
Baardsen) wrote:
>Is there any way to check if printer is active in access 2000?
>I have a report that is printing (local printer), and before I do
>anything more in code, I do want to check if printer is active.
>Do I access the windows messaging system or...?
>Anybody got a clue? Printers do funny things like "jam", run out of toner, print the wrong
way, print with lines on them, and even lose printing jobs that makes
any automated methods for determining that a job has "finished" a
exercise in futility.
Arvin Miller (if memory serves) once posted a message saying that to
make sure a printing process completed successfully, he printed out an
extra page with a random number on it, and asked the user to type it
in. If what the user types in doesn't match, the job hasn't
completed. I've used that method a couple of times and it works
great, although it is a manual method.
It's also the only one you can completely rely on!

Is there anyway to make the random number invisible on the print preview.
Some users may want to save time by previewing the last page to enter the
random number into the system before retrieving the output.

I can't find a database I've done this in right now... I know I have
them, I just can't find them. (They're backed up on CD, and I'm
really too tired to look through them. Three 20 hour days in a row
has left me fairly wiped.)

If memory serves however, the Report Activate and Deactivate events
can be used to determine what mode a report is opened in. Neither
event fires when in Print mode, but do for Preview. Use those events
to toggle whether or not the text box with the random number is
populated or not.

There may be some pre-written code at the Access Web for this:
http://www.mvps.org/access/

I also have a half-memory of this, so you'll want to check it out
yourself, but the memory cells are reminding me that if you use the
On_Print event to populate the random number text box, you'll get a
new random number each time the report is "printed" whether it is in
Preview mode or not. So if a user opens the report, scrolls to the
end, then prints the report, the number on the screen won't match the
number on the printed page. Take that with a grain of salt however,
my brain cells are not as young as they used to be.
--
A Bird In The Hand Will Doo Doo On You.


I add a Activate and Deactivate event function that calls msgbox with
"Report Activate" and "Report Deactivate". The Report Activate event fires
when a report is previewed, and the Deactivate event fires when the report
is closed. There is no additional activity on these events when the report
is printed from the preview.
I did note an extra Activate after the Deactivate when I previewed and
closed the report.

These events do not fire if the report is printed without a preview.
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.