Reports don't open...on only some machines

[patjones]

Good afternoon,

I have a 2007 front end that has been distributed to about eight people. Two individuals cannot open the report that is built into the front end. It is programmed to open in print preview.

At first I thought it might somehow be a service pack issue, as I developed the front end with my SP2 version of Access 2007, and the two users in question have SP1. This turns out not to be the case, as another user in their office also running SP1 can view the report (although his version number ends in 6320.5000 whereas the other two users end in 6213.1000).

Archives on other forums indicate that it could be a printer driver issue, but that's a hard possibility for me to test out as I am not a network person and have limited access to IT.

Any ideas? Thanks.

Pat

[ADezii]

Good afternoon,

I have a 2007 front end that has been distributed to about eight people. Two individuals cannot open the report that is built into the front end. It is programmed to open in print preview.

At first I thought it might somehow be a service pack issue, as I developed the front end with my SP2 version of Access 2007, and the two users in question have SP1. This turns out not to be the case, as another user in their office also running SP1 can view the report (although his version number ends in 6320.5000 whereas the other two users end in 6213.1000).

Archives on other forums indicate that it could be a printer driver issue, but that's a hard possibility for me to test out as I am not a network person and have limited access to IT.

Any ideas? Thanks.

Pat

It does sound like a Printer Driver issue or No Default Printer installed.

[patjones]

Thanks ADezii. The network guy says that there is no problem with the printer. I can't be sure because the two problematic users are in another building across the city; I can't see for myself. But he claims that there is no driver issue.

Maybe a bit more information will help. The report is sourced by a pass-through query that is in turn sourced by SQL Server tables. When the user clicks the button, Access deletes the previously built query, builds a new SQL string using the filters that the user selected, submits that to SQL Server, and constructs a new query with the returned results. Thus, there is a delete operation and a write operation taking place on the client end. Can this in some obscure way be a delete/write permissions issue?

Pat

[NeoPa]

Printers can be nasty beasties Pat. What may look like a single entity to a user, and even quite frequently to most network people, is actually a number of disparate entities found one per machine. I think I'm right in saying that unless the queue for the printer is held on a single PC somewhere, they are separate printers. Even in that case they may be, but if the printer is handling the queueing then they certainly are, and Access would be unlikely to recognise them as the same, even if most humans may believe them to be.

[patjones]

The network guy over there could not find any issue with the printer. So, I got up off my butt and actually walked over there to get to the bottom of this.

I took my development copy of the front end with me so that I could run it on the user's computer and step through the code to see where it was hanging. When I did so, I found that it was executing perfectly! Still no report.

Then I went into the property sheet for the report, and noticed that I had Pop Up set to "Yes". This didn't seem quite right to me, because my intention was in fact to have it open full screen as a tabbed document. So I switched Pop Up to "No", and viola - it worked.

This does not explain why other users had no problem, or even why I had no problem; however, I'm going to accept it. Thanks guys.

[NeoPa]

Good to hear you found a way to get it to work at least Pat :-)