You're welcome, Doyce. As I said, Win 7 has tons of drivers. Windows update can usually find the one you want if you don't already have it.
That's one of the best things about Win7.
Bill
--- In MS_Access_Professionals@yahoogroups.com, "dnwinberry" <winberry.doyce@...> wrote:
>
> Bill,
>
> Must have been the driver. I connected the printer to the windows 7 PC. Then installed the printer driver again. Since it did not show up in the list, I clicked Windows Update and it downloaded more drivers. Then it did show up and I installed the driver. Then I removed the printer and put it back on the XP machine and changed the port on the Win 7 PC to the port that I had originally setup for the printer on the XP machine. Now Access prints to it just fine.
>
> Thanks for helping me think this through.
>
> Doyce
>
>
> --- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@> wrote:
> >
> > Doyce
> >
> > That sounds like the issue...a partially compatable driver. You might have to get a new printer. Have you tried letting Windows find the driver? Windows 7 has a plethora of drivers. Maybe you'll get lucky. Or contact the printer company's support to see what they have to offer.
> >
> > Bill
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "dnwinberry" <winberry.doyce@> wrote:
> > >
> > > Bill,
> > >
> > > Yes the printer and address are the same. When I first tried to install, I got a message that the driver was not compatible and I could not find a 64 bit driver to add to the shared printer. So I installed it to a local port to get Win 7 to assign a driver, then I changed the port to reflect the PC that it is actually attached to. The only snag I saw in that was that Win 7 did not list a driver for a 3410. It did list one for a 4410 so I chose that one and it prints fine with that driver. Then I changed the name of the printer from 4410 to 3410 thinking Access would read the name and use that driver, however there must be something else in there causing Access to think it is a different printer. I jost don't know what.
> > >
> > > Doyce
> > >
> > > --- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@> wrote:
> > > >
> > > > Doyce
> > > >
> > > > Is the printer still at the same address in your printers folder? I sounds like maybe the port or the server path might be different. Installing the new driver might have changed something.
> > > >
> > > > Regards,
> > > > Bill Mosca, Founder - MS_Access_Professionals
> > > > http://www.thatlldoit.com
> > > > Microsoft Office Access MVP
> > > > https://mvp.support.microsoft.com/profile/Bill.Mosca
> > > >
> > > >
> > > >
> > > > --- In MS_Access_Professionals@yahoogroups.com, "dnwinberry" <winberry.doyce@> wrote:
> > > > >
> > > > > Hello Friends,
> > > > >
> > > > > I have just started using a new Win7 64 bit PC. My biggest headache so far has been setting up 64 bit printer drivers. We have an old Okidata dot matrix printer attached to a 32 bit XP computer that we use for printing multipart shipping documents. I do this from a database in Access 2007 with the report configured to print at a specific printer. I added a printer driver for it in Win 7 however, I must have not gotten something quite right because when I try to print the shipping documents I get "This document was previously formatted for the printer \\RDA286526\Okidata ML Pacemark 3410 on LPT 1:, but that printer isn't available. Do you want to use the default printer?" I can select the setup button and choose the specific printer and select Okdidata ML Pacemark 3410 and it prints fine. Why doesn't it automatically find this printer? I'm afraid if I change the db, it won't work for the other users. Any ideas?
> > > > >
> > > > > Doyce
> > > > >
> > > >
> > >
> >
>
Tidak ada komentar:
Posting Komentar