Error when printing in Vista O/S and Access 2003

[MikeP125]

I have Access 2003 running on Vista. I just got a new work station with
Vista. In the past, this database worked flawlessly in XP. I am receiving
this error
message when I try to open a report in Vista only:

"There has been a problem retreiving printer information for this object.
The object may have been sent to a printer that is unavailable."

There is a default printer which is working for other programs. I cannot
print the report from Access. The database still prints fine when running
from a workstation with XP. Please let me know if there are any bugs and/or
fixes available.
Thanks,
Mike

 

[boblarson]

First of all, have you set your MSAccess.EXE file to run as administrator?

See here for more info:

http://www.btabdevelopment.com/main...ista/RunasAdministrator/tabid/87/Default.aspx


--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
If my post was helpful to you, please rate the post.
__________________________________

 

[MikeP125]

No, I did not do this. I will not be back in the office for two weeks, so I
will not be able to try this for until then. I will let you know if this
solves the problem. Thank you for your speedy response...Mike

 

[George Nicholson]

Since it is specifically Printer related, u might try (in windows) deleting
the Default printer on that PC and then recreating it. Then see if Access
acknowledges its existance.

 

[MikeP125]

I never thoght this would work, but it did!! You are a genius! Thank
you...Mike

 

[MikeP125]

I may have spoken too soon. I was just informed after the Vista PC was
rebooted, the error message came back. There is only one printer setup and
it works perfectly with all other programs except the Access databases. The
error message "The Microsoft Jet database engine could not find the object .
Make sure the object exists and that you spell its name and the path name
correctly."

Even form the database window I cannot even open the report in design view.
This is driving me crazy! Any more thoughts?

 

[George Nicholson]

You won't be able to open reports in design view if Access doesn't have any
printer information. It can't do WYSIWYG without a known printer driver to
interact with.

Check your printer manufacturer and see if there is an updated driver for
Vista? If so, try the delete & reinstall default printer routine again and
see if Access acknowledges it after a reboot.

If all else fails, within Access: File>PageSetup (or the 2007 equivalent),
and see if you can jumpstart a printer connection that way.

 

[Vincent]

MikeP125 a écrit :

I have Access 2003 running on Vista. I just got a new work station with
Vista. In the past, this database worked flawlessly in XP. I am receiving
this error
message when I try to open a report in Vista only:

"There has been a problem retreiving printer information for this object.
The object may have been sent to a printer that is unavailable."

There is a default printer which is working for other programs. I cannot
print the report from Access. The database still prints fine when running
from a workstation with XP. Please let me know if there are any bugs and/or
fixes available.
Thanks,
Mike

I have this same problem with some clients, and I managed to gather some
more information (but unfortunately no answer so far) :

The database my clients use runs flawlessly on XP and on Vista, when the
vista stations are part of a workgroup.


Alas, when they use a Vista Worstation as part of a windows Server 2003
domain, I have no way to edit, view or print a report. I can't even
create one, since creating a report requires editing it...

To add even more trouble to it, when I try to change the msaccess
properties to set "run as administratior", the combo box is greyed,
wether I log in as a user, a domain administrator, a machine
administrator, or god knows what else (believe me I TRIED all the
accounts)... yay ! thank you Bill Gates, really, cheers...

So if anyone has an idea or can get some sudden enlightment from the
remarks...

cheers,

Vince