G
Guest
I have an Access 2000 application that is split front end (workstation) /
back end (network). The application has been running 3 years with no
problems/no changes in the area of printing. We moved from a Novell Network
to a Windows Server 2003 network recently. All normal print previewing,
then printing seems to be fine. Within the printing, there is a section
where the user can request to print and collate a report. It actually
involves previewing all of the reports and then going through a loop to
..SelectReport and .Printout 1 page of each of the 5 reports. Since we've
moved to the Windows Server, we are having problems with the headings being
lost while printing....on some of the reports. The problem is only present
in the beginning pages of the print process, after about 300 pages, it prints
all reports and headings fine. I added a "Sleep" for 1 second after each
Printout. That solved seemed to solve it that day, but now the problem is
back. I suspect its related to the network traffic or possibly printer
traffic. Any suggestions on how to completely solve this problem? Thanks
back end (network). The application has been running 3 years with no
problems/no changes in the area of printing. We moved from a Novell Network
to a Windows Server 2003 network recently. All normal print previewing,
then printing seems to be fine. Within the printing, there is a section
where the user can request to print and collate a report. It actually
involves previewing all of the reports and then going through a loop to
..SelectReport and .Printout 1 page of each of the 5 reports. Since we've
moved to the Windows Server, we are having problems with the headings being
lost while printing....on some of the reports. The problem is only present
in the beginning pages of the print process, after about 300 pages, it prints
all reports and headings fine. I added a "Sleep" for 1 second after each
Printout. That solved seemed to solve it that day, but now the problem is
back. I suspect its related to the network traffic or possibly printer
traffic. Any suggestions on how to completely solve this problem? Thanks