G
Guest
We have an access application, not designed by us. This prints reports for
students for members of staff. I 'inherited' this problem from my predecessor.
When some users open it they get the "There was a problem retrieving printer
information for this object. The object may have been sent to a printer which
is unavailable".
This does not affect all users, users can move from one machine to another
and not get the problem - this suggests it's not the user account or profile
The printers are not the same model, all our printers are network printers
on the same server and all printers of the same model do not fault - this
suggests it's not the printer driver
I can log in on one workstation which always has the fault, and get the
error, I can move to another workstation and install the same printer as
default printer and not get the error - this suggests it's not the print
queue on the server
This rather leaves me suspecting the setup of Access on the workstation. All
our workstations are built from the same image and 'should' therefore have an
identical access installation. I've looked at KB 294555, but most of those
solutions seem to be based around printers and print drivers which I think
I've discounted (see above). The regional settings on the workstations look
fine to me.
Any suggestions gratefully revieved?
students for members of staff. I 'inherited' this problem from my predecessor.
When some users open it they get the "There was a problem retrieving printer
information for this object. The object may have been sent to a printer which
is unavailable".
This does not affect all users, users can move from one machine to another
and not get the problem - this suggests it's not the user account or profile
The printers are not the same model, all our printers are network printers
on the same server and all printers of the same model do not fault - this
suggests it's not the printer driver
I can log in on one workstation which always has the fault, and get the
error, I can move to another workstation and install the same printer as
default printer and not get the error - this suggests it's not the print
queue on the server
This rather leaves me suspecting the setup of Access on the workstation. All
our workstations are built from the same image and 'should' therefore have an
identical access installation. I've looked at KB 294555, but most of those
solutions seem to be based around printers and print drivers which I think
I've discounted (see above). The regional settings on the workstations look
fine to me.
Any suggestions gratefully revieved?