Some users cannot run reports

I have a database that was written in Access 2000. It's on a network,
and some users run it with Access 2000, but one computer runs it with
Access 2003. This worked fine while we were sharing it on a Netware
4.12 server. Last week we replaced that server with a Microsoft Server
2003. Now the Access 2000 users can run the reports, and I'm the only
one that can run them with Access 2003. On the same computer other
users cannot run reports, even if I make them local administrators.

When they try to run reports from a form, they get "The OpenReport
action was canceled." If they try to run reports from the Access
reports menu, nothing happens.

I have installed "Microsoft Jet 4.0 Service Pack 8" on the 2003
computer and set macro security to low.

I'm at a loss -- help!!

thx . . . Frank

Interesting that one of our users is having the exact same problem and I went
through all of the same steps in order to try and solve. This user was just
upgraded to office 2003. We even reinstalled office. It's as if the reports
don't exist for this one user. And -- yes this pc does have a default
printer defined.
Any other suggestions would be much appreciated. Thank you.

"Duane Hookom" wrote:

Make sure all of the pcs have a default printer defined in Windows.

--
Duane Hookom
MS Access MVP
--

"Frank" wrote in message
oups.com...
I have a database that was written in Access 2000. It's on a network,
and some users run it with Access 2000, but one computer runs it with
Access 2003. This worked fine while we were sharing it on a Netware
4.12 server. Last week we replaced that server with a Microsoft Server
2003. Now the Access 2000 users can run the reports, and I'm the only
one that can run them with Access 2003. On the same computer other
users cannot run reports, even if I make them local administrators.

When they try to run reports from a form, they get "The OpenReport
action was canceled." If they try to run reports from the Access
reports menu, nothing happens.

I have installed "Microsoft Jet 4.0 Service Pack 8" on the 2003
computer and set macro security to low.

I'm at a loss -- help!!

thx . . . Frank

Unselect and then reselect the default printer in Windows and make sure the
latest drivers are loaded.

Try change the default printer to another printer.

--
Duane Hookom
MS Access MVP
--

"Suzanne" wrote in message
...
Interesting that one of our users is having the exact same problem and I
went
through all of the same steps in order to try and solve. This user was
just
upgraded to office 2003. We even reinstalled office. It's as if the
reports
don't exist for this one user. And -- yes this pc does have a default
printer defined.
Any other suggestions would be much appreciated. Thank you.

"Duane Hookom" wrote:

Make sure all of the pcs have a default printer defined in Windows.

--
Duane Hookom
MS Access MVP
--

"Frank" wrote in message
oups.com...
I have a database that was written in Access 2000. It's on a network,
and some users run it with Access 2000, but one computer runs it with
Access 2003. This worked fine while we were sharing it on a Netware
4.12 server. Last week we replaced that server with a Microsoft Server
2003. Now the Access 2000 users can run the reports, and I'm the only
one that can run them with Access 2003. On the same computer other
users cannot run reports, even if I make them local administrators.

When they try to run reports from a form, they get "The OpenReport
action was canceled." If they try to run reports from the Access
reports menu, nothing happens.

I have installed "Microsoft Jet 4.0 Service Pack 8" on the 2003
computer and set macro security to low.

I'm at a loss -- help!!

thx . . . Frank

We are using printers shared off the server on this network. I have
removed and reattached it for that user and even installed it as a
local printer using TCP/IP. Still no go. I'm not there today, but
I'll email them to attach to a different printer and give it a try.
Thanks for the replies.

Frank wrote:
We are using printers shared off the server on this network. I have
removed and reattached it for that user and even installed it as a
local printer using TCP/IP. Still no go. I'm not there today, but
I'll email them to attach to a different printer and give it a try.
Thanks for the replies.

They reported back that she can print today. Go figure. I'm guessing
that removing and reinstalling printers last Thursday did something to
solve the problem, but maybe it didn't affect a solution until she'd
restarted the computer instead of just logging out.

Thanks for the suggestions.

We did the same and was a no go for us also. We think we have isolated the
problem to XP. The same user can log on another PC in the network using
Windows 2000 and the reports work fine. Using a PC on the network with XP
that was upgraded from 2000 also works fine. Using a PC on the network with
a clean install XP replicates the problem. Any other suggestions? Thank you
very much.


"Frank" wrote:


Frank wrote:
We are using printers shared off the server on this network. I have
removed and reattached it for that user and even installed it as a
local printer using TCP/IP. Still no go. I'm not there today, but
I'll email them to attach to a different printer and give it a try.
Thanks for the replies.

They reported back that she can print today. Go figure. I'm guessing
that removing and reinstalling printers last Thursday did something to
solve the problem, but maybe it didn't affect a solution until she'd
restarted the computer instead of just logging out.

Thanks for the suggestions.

Define a different default printer for a test.

--
Duane Hookom
MS Access MVP
--

"Suzanne" wrote in message
...
We did the same and was a no go for us also. We think we have isolated
the
problem to XP. The same user can log on another PC in the network using
Windows 2000 and the reports work fine. Using a PC on the network with XP
that was upgraded from 2000 also works fine. Using a PC on the network
with
a clean install XP replicates the problem. Any other suggestions? Thank
you
very much.


"Frank" wrote:


Frank wrote:
We are using printers shared off the server on this network. I have
removed and reattached it for that user and even installed it as a
local printer using TCP/IP. Still no go. I'm not there today, but
I'll email them to attach to a different printer and give it a try.
Thanks for the replies.

They reported back that she can print today. Go figure. I'm guessing
that removing and reinstalling printers last Thursday did something to
solve the problem, but maybe it didn't affect a solution until she'd
restarted the computer instead of just logging out.

Thanks for the suggestions.

Duane,
We tried that. Any other suggestion? Thanks

"Duane Hookom" wrote:

Define a different default printer for a test.

--
Duane Hookom
MS Access MVP
--

"Suzanne" wrote in message
...
We did the same and was a no go for us also. We think we have isolated
the
problem to XP. The same user can log on another PC in the network using
Windows 2000 and the reports work fine. Using a PC on the network with XP
that was upgraded from 2000 also works fine. Using a PC on the network
with
a clean install XP replicates the problem. Any other suggestions? Thank
you
very much.


"Frank" wrote:


Frank wrote:
We are using printers shared off the server on this network. I have
removed and reattached it for that user and even installed it as a
local printer using TCP/IP. Still no go. I'm not there today, but
I'll email them to attach to a different printer and give it a try.
Thanks for the replies.

They reported back that she can print today. Go figure. I'm guessing
that removing and reinstalling printers last Thursday did something to
solve the problem, but maybe it didn't affect a solution until she'd
restarted the computer instead of just logging out.

Thanks for the suggestions.

This is almost always due to a printer either not being defined or with an
old driver. Try would try various local and network printers and confirm the
latest drivers.

--
Duane Hookom
MS Access MVP


"Suzanne" wrote in message
...
Duane,
We tried that. Any other suggestion? Thanks

"Duane Hookom" wrote:

Define a different default printer for a test.

--
Duane Hookom
MS Access MVP
--

"Suzanne" wrote in message
...
We did the same and was a no go for us also. We think we have isolated
the
problem to XP. The same user can log on another PC in the network
using
Windows 2000 and the reports work fine. Using a PC on the network with
XP
that was upgraded from 2000 also works fine. Using a PC on the network
with
a clean install XP replicates the problem. Any other suggestions?
Thank
you
very much.


"Frank" wrote:


Frank wrote:
We are using printers shared off the server on this network. I have
removed and reattached it for that user and even installed it as a
local printer using TCP/IP. Still no go. I'm not there today, but
I'll email them to attach to a different printer and give it a try.
Thanks for the replies.

They reported back that she can print today. Go figure. I'm guessing
that removing and reinstalling printers last Thursday did something to
solve the problem, but maybe it didn't affect a solution until she'd
restarted the computer instead of just logging out.

Thanks for the suggestions.

Dear all, I had the same problem Suzanne has... I tried to switch to another
printer and... it works!!! The question is: how can Microsoft make us nice
"presents" like the one we're dealing about???

Thanks for your suggestion
David

"Duane Hookom" wrote:

This is almost always due to a printer either not being defined or with an
old driver. Try would try various local and network printers and confirm the
latest drivers.

--
Duane Hookom
MS Access MVP


"Suzanne" wrote in message
...
Duane,
We tried that. Any other suggestion? Thanks

"Duane Hookom" wrote:

Define a different default printer for a test.

--
Duane Hookom
MS Access MVP
--

"Suzanne" wrote in message
...
We did the same and was a no go for us also. We think we have isolated
the
problem to XP. The same user can log on another PC in the network
using
Windows 2000 and the reports work fine. Using a PC on the network with
XP
that was upgraded from 2000 also works fine. Using a PC on the network
with
a clean install XP replicates the problem. Any other suggestions?
Thank
you
very much.


"Frank" wrote:


Frank wrote:
We are using printers shared off the server on this network. I have
removed and reattached it for that user and even installed it as a
local printer using TCP/IP. Still no go. I'm not there today, but
I'll email them to attach to a different printer and give it a try.
Thanks for the replies.

They reported back that she can print today. Go figure. I'm guessing
that removing and reinstalling printers last Thursday did something to
solve the problem, but maybe it didn't affect a solution until she'd
restarted the computer instead of just logging out.

Thanks for the suggestions.