S
Sandy
I support a db app for five separate locations. In four locations my
end-users can print from Access fine. However, in one location, when the
end-users log into the .mdb and they pull up a "complicated" report, and then
select Print from the toolbar, the data begins to go to the spooler, but it
times out and never finishes spooling and therefore, does not print.
The end-users in all locations are printing to a network printer at their
specific location.
I have used the immediate window to identify whether or not the .mdb
recognizes the printer, and it does. (using Applications.Printer.DeviceName,
etc.)
The end-users can print from other applications just fine, even when the
print command has been initiated from Access, they can open another
application and print to the same printer (so it is not a printer memory
issue).
I had the end-user re-install their network printer, and it did not resolve
this problem.
I have roughly 14 users logging into the same .mdb file and they experience
a delay in pulling the report due to the complexity and the amount of users
logged in.
I tried a "distributed" front-end, where the users have their own copy of
the .mdb, with the tables linked as in the original, to the backend .mdb.
This does not resolve the print issue either.
I'm resolving that they are having a network issue, however, why can they
print from other applications, but not Access?
The .mdb is an Access 2000 file format, running on Microsoft Professional XP
with Microsoft 2003 products.
I hope someone out there has experienced this issue, or can point me in the
direction of information regarding it.
Thank you in advance for your help!
end-users can print from Access fine. However, in one location, when the
end-users log into the .mdb and they pull up a "complicated" report, and then
select Print from the toolbar, the data begins to go to the spooler, but it
times out and never finishes spooling and therefore, does not print.
The end-users in all locations are printing to a network printer at their
specific location.
I have used the immediate window to identify whether or not the .mdb
recognizes the printer, and it does. (using Applications.Printer.DeviceName,
etc.)
The end-users can print from other applications just fine, even when the
print command has been initiated from Access, they can open another
application and print to the same printer (so it is not a printer memory
issue).
I had the end-user re-install their network printer, and it did not resolve
this problem.
I have roughly 14 users logging into the same .mdb file and they experience
a delay in pulling the report due to the complexity and the amount of users
logged in.
I tried a "distributed" front-end, where the users have their own copy of
the .mdb, with the tables linked as in the original, to the backend .mdb.
This does not resolve the print issue either.
I'm resolving that they are having a network issue, however, why can they
print from other applications, but not Access?
The .mdb is an Access 2000 file format, running on Microsoft Professional XP
with Microsoft 2003 products.
I hope someone out there has experienced this issue, or can point me in the
direction of information regarding it.
Thank you in advance for your help!