A
Andy Williams
Sorry to bring this up again, but I haven't gotten any responses. Certainly
someone's come across this same problem. I'm curious to see how others have
been able to deal with this.
Originally posted on 8/26/03, crossposting to setupconfig NG:
-------------------------------------------------------
I have an Access 2000 project that has run great for three years, but the
introduction of Windows XP machines has caused a major problem with printing
reports. Basically, if a report is set to print to a specific printer, it
will work on the machine that has the local printer, but the same .adp file
run on another PC will prompt to select a printer, even though the printer
is set up on that PC.
Most of the reports in the project just print to the local printer, but the
reports that print to the impact and label printers need to be run from any
machine. My work around has been to maintain separate copies of the adp for
each user, but I'd like to eventually release one ade that works for
anyone.
Any ideas would be greatly appreciated.
someone's come across this same problem. I'm curious to see how others have
been able to deal with this.
Originally posted on 8/26/03, crossposting to setupconfig NG:
-------------------------------------------------------
I have an Access 2000 project that has run great for three years, but the
introduction of Windows XP machines has caused a major problem with printing
reports. Basically, if a report is set to print to a specific printer, it
will work on the machine that has the local printer, but the same .adp file
run on another PC will prompt to select a printer, even though the printer
is set up on that PC.
Most of the reports in the project just print to the local printer, but the
reports that print to the impact and label printers need to be run from any
machine. My work around has been to maintain separate copies of the adp for
each user, but I'd like to eventually release one ade that works for
anyone.
Any ideas would be greatly appreciated.