Disable Ctrl-p for specific reports

[Keven Denen]

I must be missing something simple here.

How can I disable ctrl-p as a keyboard shortcut for print on a couple
specific reports? I've removed the menu option and toolbar option for
those reports, but users are still able to print using ctrl-p.

Keven Denen

 

[gerard del marie]

I must be missing something simple here.

How can I disable ctrl-p as a keyboard shortcut for print on a couple
specific reports? I've removed the menu option and toolbar option for
those reports, but users are still able to print using ctrl-p.

Keven Denen

 

[Douglas J. Steele]

I don't believe it's possible just for certain reports: I think it's an
all-or-nothing proposition whereby you create an AutoKeys macro and reset
what Ctrl-P does.

 

[Dirk Goldgar]

I must be missing something simple here.

How can I disable ctrl-p as a keyboard shortcut for print on a couple
specific reports? I've removed the menu option and toolbar option for
those reports, but users are still able to print using ctrl-p.

It's kind of an odd request -- why use a report if you're not ever going to
let the user print it? -- so I can understand why there's no simple way to
suppress it. How about this: set up an AutoKeys macro for the Ctrl+P key
combination, and begin that macro with a StopMacro action that is
conditional on whether Screen.ActiveReport.Name is one of the reports whose
printing you want to suppress. Follow that action with a PrintOut action
that should handle any other object, so that Ctrl+P will work for them.

 

[Keven Denen]

It's kind of an odd request -- why use a report if you're not ever going to
let the user print it? -- so I can understand why there's no simple way to
suppress it.  How about this:  set up an AutoKeys macro for the Ctrl+P key
combination, and begin that macro with a StopMacro action that is
conditional on whether Screen.ActiveReport.Name is one of the reports whose
printing you want to suppress.  Follow that action with a PrintOut action
that should handle any other object, so that Ctrl+P will work for them.

--
Dirk Goldgar, MS Access MVP
Access tips:www.datagnostics.com/tips.html

(please reply to the newsgroup)

It's mostly laziness on my part. I already have the report created for
the managers of the company. They want their sales reps to be able to
see the report, but not print it. I could take the time to make a form
to duplicate the report, but it's a fairly complicated report and I
didn't want to go through the hassle of recreating it as a form.

I solved this by using the Autokeys macro to run code and then in the
code determined which report was on-screen (thanks for that code Dirk)
and either brought up the Print Dialog or pop an error message to
indicate that reps don't have permission to print.

Keven Denen

 

[John W. Vinson]

They want their sales reps to be able to
see the report, but not print it.

Absurd. Dilbert style pointy haired boss thinking!

There is NO way for Access to prevent the reps using screen capture software,
or copying and pasting the image to Word, or taking a cell phone photograph of
the screen.

They're looking for a technical solution to a (probably non-existant)
personnel problem.

 

[David W. Fenton]

Absurd. Dilbert style pointy haired boss thinking!

There is NO way for Access to prevent the reps using screen
capture software, or copying and pasting the image to Word, or
taking a cell phone photograph of the screen.

They're looking for a technical solution to a (probably
non-existant) personnel problem.

Which gives me an opportunity to say once again that most security
problems are actually people problems in disguise.

 

[John W. Vinson]

Which gives me an opportunity to say once again that most security
problems are actually people problems in disguise.

The worst security breach that I was ever involved in involved a corporate
research VP who requested copies of a number of confidential research
protocols. Seemed rather odd - they weren't directly in his area of
responsibility - but he was a VP and had every right to them.

In less than a week he'd resigned and gone to California to found a new
competing startup company doing research in... well, you guessed it.