Each user prints the same report to a different printer

[Paul H]

My database is a FE/BE Access 2000 database installed on 3 XP workstations.

Each user has a different model of label printing machine attached to their
PCs:

Workstation 1 has a Label printer model 200
Workstation 2 has a Label printer model 320
Workstation 3 has a Label printer model 400

All the above models all print to the same size label (with a bit of
tweaking).

There is a button on one of the forms called "Print Address Label" that runs
the following code:

DoCmd.OpenReport "rptLabel", acViewNormal

Everytime the client requests a minor update on the database, I have to
manually copy the new front end to each PC and reconfigure the "rptLabel"
report on each PC to print to the specific model of label printer attached
to the PC otherwise the user gets this message:

"This document was previously formatted for the printer DYMO Labelwriter 400
on USB003, but the printer isn't available.....etc.."

It's a pain. I want to be able to roll out a single updated FE file and the
users do not want have to select a printer every time they print a label.

The client does not want to share a single printer because each user wants a
printer on their own desk. So I have suggested that they buy two more model
400 printers to replace the older models, so that every one is using the
same model.

Would this alone solve the roll out problem? Or will I have to start messing
with printer APIs and other nasties? (Notice that the message above
mentioned that it was expecting to find the Labelwriter 400 on USB003).

Thanks

Paul

[BillCo]

if you dont want to mess with api stuff here's a quick and dirty work
around (but you're stuffed if your users switch machines). Have three
versions, each formatted in the required way. then print selectively
based on user name:

Select Case Environ("USERNAME")
Case "UserNameA"
'launch report a
case "UserNameB"
'launch report b
case "UserNameC"
'Launch report c
End Select

If you would prefere users to be able to swap around then you will need
to identify the computer. Search for getting the computers Mac address
from API with VBA to do this.

The best solution though, would be to identify the physical label
printer connected. I'm sure there's an API for it, but I can't help you
with that one.

[Tom van Stiphout]

On Thu, 9 Nov 2006 11:56:36 -0000, "Paul H" <pa**@nospam.comwrote:

On Access2000 this would require a messy switching of the default
printer. On Access2002 and above MSFT finally fixed that with the
addition of the Printer object which makes the task easy.

-Tom.

>My database is a FE/BE Access 2000 database installed on 3 XP workstations.

Each user has a different model of label printing machine attached to their
PCs:

Workstation 1 has a Label printer model 200
Workstation 2 has a Label printer model 320
Workstation 3 has a Label printer model 400

All the above models all print to the same size label (with a bit of
tweaking).

There is a button on one of the forms called "Print Address Label" that runs
the following code:

DoCmd.OpenReport "rptLabel", acViewNormal

Everytime the client requests a minor update on the database, I have to
manually copy the new front end to each PC and reconfigure the "rptLabel"
report on each PC to print to the specific model of label printer attached
to the PC otherwise the user gets this message:

"This document was previously formatted for the printer DYMO Labelwriter 400
on USB003, but the printer isn't available.....etc.."

It's a pain. I want to be able to roll out a single updated FE file and the
users do not want have to select a printer every time they print a label.

The client does not want to share a single printer because each user wants a
printer on their own desk. So I have suggested that they buy two more model
400 printers to replace the older models, so that every one is using the
same model.

Would this alone solve the roll out problem? Or will I have to start messing
with printer APIs and other nasties? (Notice that the message above
mentioned that it was expecting to find the Labelwriter 400 on USB003).

Thanks

Paul

[Paul H]

Thanks folks,

Very helpful suggestions, I will probably upgrade Access and use the Printer
object.

Paul

[Albert D. Kallal]

You can also simpy set the lablel repot to use the default proitner, and DO
NOT assing the reprot to a particlar label printer.

You can then use my printer swtich code here:

http://www.members.shaw.ca/AlbertKal.../msaccess.html

So, you simply "save" which printer you want in some table, and then
'swtich' to that printer...print, and then swtich back....
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com