Urgent! Cannot create, design, open, or preview reports

[ChristineP]

Just upgraded from Windows XP/Office 2002 to to Office/Access 2003 on a brand
new computer.

Before the upgrade and now with the upgrade as well, I cannot do anything
with reports: cannot preview, open, design or create new. No error messages
are displayed.

Also, in the Report Wizard, it gets as far as "What title to you want to
give your report?" and then displays the error message "The wizard is unable
to create your report".

I have tried creating new databases, thinking mine were corrupted, but it
doesn't make any difference. Can someone please help ASAP?

 

[RC via AccessMonster.com]

I experienced something similar. I'll assume you have set up printers on
your new pc. If not, this is why your report function doesn't work. In my
case, the fix was to change my default printer. For some reason, the
report function worked on some printers, but not all. I don't why this is
the case, but that's the fix...in my case. Hope this helps you out.

 

[ChristineP]

Thanks for that! I see that Printer commands are dimmed and it says "No
printer" when you click on, for example, the printer icon on the toolbar. How
to I let Access know there is a printer?

Thanks!

 

[Alex White MCDBA MCSE]

Have you installed a new printer on the new computer if so make sure it is
the default printer by going into the printers folder and right mouse
clicking on the printer and set it to the default printer make sure that you
can print a test page. The reason you need this is access does not know how
to render the page without a default printer.

 

[ChristineP]

I have six printers available and all work just fine from all other
applications.
After my last post I realised that I CAN print code from any of the six
installed printers, so Access is obviously seeing something! I can't do
anything with reports, as I said before, but also see I cannot print tables
(the commands for Print and Page setup are not dim but, but they don't do
anything.)

This is becoming a serious problem!!

 

[ChristineP]

Also wanted to say, if I try to open a report from code, I get the error
"Runtime error 2501."

 

[Alex White MCDBA MCSE]

Can you try and create a blank database and just create one table, one
report and see if that works, need to see if the problem is with the
specific mdb or access or the computer somehow. If you figure out it is the
installation, do a reinstall, update all the service packs for windows
http://windowsupdate.microsoft.com office http://officeupdate.microsoft.com
and mdac/jet http://www.microsoft.com/data and your default printers printer
driver.

Post back if you are still having problems.

 

[RC via AccessMonster.com]

Give this a try. It "kick started" the Access reports function in some of
our newly upgraded Windows XP/Office 2003 pc's:

- Add a new printer: in the wizard, select Local Printer, Port = File(Print
To File), Driver = Generic/Text Only.
- Make it your default printer.
- Open your database, and see if you can go to report design view now.
- If so, go to File > Page Setup and select "Default Printer". Save report.
Print the report. Remember it will print to some dummy file you specify.
- If you get this far, on the same report, go to File > Print and now
change the printer destination to a valid printer.

 

[ChristineP]

First, thanks to Alex for his suggestions. I had tried creating a blank
database but that didn't work. The computer is brand new but I checked for
updates and I'm current.

To RC, Yes - installing the generic printer worked! However, when I switched
back to my normal printer (HP Laserject on a network), the fonts are all
jumbled. Rebooting had no effect. When I switch to a Ricoh Aficio 2027 RPCS
it works okay, although the reports and wizard work VERY, VERY
slooooooooowly. A switch to a Xerox 8830 works much faster. So, it appears it
might be an issue with the driver for the HP. I'll ask MIS to switch it for
me - however they just swiched drivers because Word 2003 had an issue with
the old one. If it's not one thing with Microsoft it's another!

Many thanks for your help, Alex and RC - I'd never have thought to look at
printer drivers for this problem.