Access 2003 - "Unable to Create Report"

[Lost in Access]

When attempting to create a report (via the wizard), I get the msg "The
wizard is unable to create your report". I understand that this may be due
to printer setup issues, but am not sure how to resolve. Other relevant
facts:

- Access 2003/Vista
- I have printers installed & print regularly from other applications
- When I try to print. print preview, or page setup while looking at a
table (or form), nothing happens (I'm new to access, but it seems like I
should be able to print a table?!) - as in I select any of the above options
and nothing happens.

Other posts seem to suggest something about a local port solution - I'm not
sure exactly what this means (do I need to setup a new printer in a different
fashion than my existing printer?)

Am very grateful for any help that can be offered. Thx in advance!

 

[Evi]

What happens if you click on any (really simple) query, go to Insert and
choose Report. Then choose Autoreport?
Lets see if its only the wizard who fouls up or if the fault lies with the
report itself.
Evi

 

[Lost in Access]

I tried it a couple of different ways with no success:

After selecting a simple Query:

- Insert, Report, AutoReport: Columnar; resulted in same msg ("wizard unable
to create report")
- same thing happens if I try it with tabular
- if I choose Insert, Report, "Design View", nothing happens at all.

Thanks again for your help!

 

[Evi]

It does sound like a printer driver thing but why it should only affect
access is anyone's guess.

I know this is a long shot but do you have any Reserved Words as your field
names?
http://support.microsoft.com/kb/286335/en-us
This article describes a problem with printing (although not the one you
describe) when you have reserved words. The list given is not complete.
Evi

 

[Lost in Access]

I don't believe the reserved words is the issue, but to be safe I changed the
only field name that was close & it didn't help. Also, to be sure the issue
wasn't unique to this file, I downloaded a standard MS template ("Accounts
Ledger"). I was unable to open the existing reports they have in the
template (selecting a report and clicking 'preview' or 'design' or double
clicking does nothing - trying to use the wizard results in the same error
msg).

Is there a way I can reinstall the printers - just to be sure that this
isn't the root cause? I'm not sure what other options I have at this point?

 

[Evi]

Try this - it solved a report preview user for one Acc2003Vista user
Click Start, click Run, type, regsvr32.exe
C:\Windows\System32\msjtes40.dll, and then click OK.
Evi. When registration finishes, click OK.
you may need to change the file path to your version of msjtes40.dll

 

[Evi]

is there anything in this article that applies?
http://support.microsoft.com/kb/294555/en-us

I've got a feeling you won't be the last person with this problem

Evi

 

[Lost in Access]

Ran the "regsvr32.exe C:\Windows\System32\msjtes40.dll" command (it appeared
to work properly) & restarted the computer. Unfortunately it doesn't appear
to have had any impact to MS Access (same as initial - no ability to
view/preview/create reports).

(thanks again for your continued suggestions - I'm still holding out hope
that there's a solution)

 

[Ed Cones]

Same problem here. Access 2003 SP3 on an XP Professional machine.

I get the same error with the report wizard, and double-clicking "Create
report in Design view" just does nothing.

 

[Ed Cones]

I've discovered that the report wizard and report design view works fine if
I'm logged in as an administrator. It doesn't work if I'm logged in as a
limited user. Giving users full permissions to C:\Program Files\Microsoft
Office did not fix the problem.

I'd appreciate any suggestions of what permissions should be given to our
limited users. Unfortunately, I'm not allowed ot make users Power Users.

 

[Evi]

Do you have a Default Printer set?
Evi

On XP, I had to recreate the local user profile to get this same situation
fixed. I have not yet gotten down to where the problem actually lies in the
registry, but there is something for you.