Can't open reports in Access 2003

[DonS100]

Hello, I'm using access 2003 and can't get the reports to work. When I try to create a new report or open a existing report it doesn't open. I've tried reinstalling Office 2003 but this didn't fix the issue.

Any clue where I should start looking to fix this?

Thanks

Don

 

[THWatson]

Don
Do you get any error message? Is there a chance that you need to download the latest version of Jet?

I just did a quick search on Microsoft Knowledge Base and there is an article, #838911, that relates to that.

I am interested in this because I was considering installing Office 2003 (currently using 2000) and am trying to foresee any issues ahead of doing so.

I would be interested in whatever you discover.

Tom

 

[DonS100]

Nope, Don't get a error message. I was able to fix them problem by changing by default printer.

 

[THWatson]

Glad it was so easy a fix. Thanks for letting me know.

Tom

 

[cipcfh]

thanks a lot for the tip! i thought i was having security issues with my workstation. what a relief!

 

[Rob98765]

Thanks a lot. I was pulling out hair. This has got to be considered a bug.

 

[THWatson]

In case any of you are interested, I installed Access 2003 on my laptop but not on my desktop computer, and here are some things I discovered about Access 2003. Going from Access 2000 to 2003 is far from a seamless proposition. There are a number of issues.

1. If you apply a Digital Certificate using Access 2003 (in order to get around the annoying security messages) and then attempt to use the database on a computer running Access 2000 you cannot edit any VBA code. This happens even if using the default file format of Access 2000.

2. In Access 2000 there is a HasData property, to check to see whether or not a subreport has data. If you don't do that check and there is no data in the subreport you get a #Error. However, Access 2003 doesn't seem to have the HasData property, so any controls with that expression show up empty.
So if you have two computers, one running Access 2003, the other running Access 2000, even though the file format is Access 2000 (the default), controls with the HasData property show properly on the computer running 2000 but show blank on the computer running 2003.
I have searched the Microsoft Knowledge Base but cannot find a reference to HasData in Access 2003, or any work-around for that property. Perhaps 2003 doesn't require this data check, even in the 2000 format, but omitting it creates a disaster with computers running 2000.

3. Using Help is irritating. Anything beyond a rudimentary question requires connection to the Internet in order for Help to check Microsoft Office Online.

4. There are frequent crashes when closing a database. For no logical reason that I can see.

Perhaps if one is using Access 2003 exclusively, there aren't as many problems. But using databases created in 2003 (in the default format of 2000) on computers running Access 2000 seems to have more problems than I would like to see.

Tom

 

[DonS100]

Has anyone found out more about this situation. I initially just switched my default printer, but at some time when I have more users using the app I can't simple tell them not to use some printers.

Thanks

Don

 

[THWatson]

I just did a search on Microsoft Knowledge Base, for Access 2003. The search was "default printer". Several articles were displayed. One of them is Article #290293.

I don't know if any of these articles will help, but they are worth looking at.

Tom

 

[Kelv1979]

I experience this issue myself. I've narrowed it down to whether my default printer is a local or network printer. For some reason, as soon as I change my default to a network printer Access 2003 reports that there is "(no printer)" when hovering over the print button on the toolbar. As there is no printer, reports cannot be used.

Unfortunately, I've only located the problem and not found the solution yet. If anybody can shed any light I'd be most grateful.

Kelv

 

[Kelv1979]

Further to the above, I've now found that it works with some network printers but not others. I'm slightly confused by this - it works with printers that have in built jet direct such as a 4200 but not those that have external network options such as Intel netports.