ctrl + p - printing reports

  • Thread starter Thread starter KB
  • Start date Start date
K

KB

Ok I give up. I want to stop users printing particular reports using crtl+p
and alt+p. It's been suggested to me to use autokey macros. I rarely if ever
use macros so not really familiar with them. While I've tracked down autokey
macros and can see how to create one it is not really obvious to me how I
might use it in a report. It's not a menu or toolbar and the report has no
print event. Anyone like to clear the way and suggest to me where the light
is in this little brain teaser?

TIA

KB
 
Sorry - I forgot to mention we still want to view the report then print it
using code for the purpose - we have a menu for that.
 
If you have a macro called Autokeys,
in which is a line were the MacroName value is ^p
and no action is set on that line,

then when you press ctrl+p nothing happens.

You may have to quit access to get the macro
to load/unload correctly.

You don't 'use' the macro at all. It just exists.
When MS developed Access, they used the macro's
to script the Access UI. (It was a long time ago).

The autokey setting doesn't prevent you from doing
anything to or with a report. It just intercepts
the scripted keystrokes.

(david)
 
Doh! I said I don't use macros much - it "runs" the same as autoexec at
startup. To flipping easy - probably so easy it's hard to find. Thank you.
 
One other one - what is the (is there a) symbol for the "alt" key? It seems
that an alt+p prints as well....
 
may have to upgrade the access version I think - it says invalid syntax or
key combination not allowed..... doh!
 
Sorry: my fault. I don't trap that many keys, so I went to the Help file. It
listed a bunch of key combinations, and had a link to the SendKeys syntax (%
is how you do it for SendKeys). I missed the fact that it said "These key
combinations are a subset of the syntax used in the SendKeys statement in
Visual Basic", implying that's all that's possible.
 
Alt P doesn't print ---- it calls the <underscore P>
menu item, which in view mode for a report happens to
be a print command. Make your own menu with your own
print command (or null action), or hide the file menu,
or ... something.

In the language of Access, [alt]p is an access key
(access as in accessibility), p is a shortcut key.

(david)
 
Ah yes that does explain it - I shall advise Microsoft that it should
provide us with access (no pun intended) to the full set of keys or block
the back door :-). It was pure accident that I tried an alt+p and I was
surprised that it worked actually.

Thanks
 
Doh! I'll check that - makes sense. I have my own menus but just maybe there
is a shortcut key combo for the print menu choice ...... mumble mumble
mumble stupid silly obvious stuff....

Thanks

david epsom dot com dot au said:
Alt P doesn't print ---- it calls the <underscore P>
menu item, which in view mode for a report happens to
be a print command. Make your own menu with your own
print command (or null action), or hide the file menu,
or ... something.

In the language of Access, [alt]p is an access key
(access as in accessibility), p is a shortcut key.

(david)


KB said:
One other one - what is the (is there a) symbol for the "alt" key? It seems
that an alt+p prints as well....



how has
Click to expand...
Click to expand...
 
Made sure there is no menu shortcuts - there aren't now BUT alt+p *still*
prints so I'm stumped. I've got my own menu, it calls my code there is no
shortcut to that menu choice BUT alt+p prints and bypasses the code. Any
body got any other ideas to check.




david epsom dot com dot au said:
Alt P doesn't print ---- it calls the <underscore P>
menu item, which in view mode for a report happens to
be a print command. Make your own menu with your own
print command (or null action), or hide the file menu,
or ... something.

In the language of Access, [alt]p is an access key
(access as in accessibility), p is a shortcut key.

(david)


KB said:
One other one - what is the (is there a) symbol for the "alt" key? It seems
that an alt+p prints as well....



how has
Click to expand...
Click to expand...
 
hmmm. must be working even without menu. BUT can you
substitute your own P menu? Although my experience with
menu's with conflicting shortcut keys is that they never
seem to work properly.

(david)

KB said:
Made sure there is no menu shortcuts - there aren't now BUT alt+p *still*
prints so I'm stumped. I've got my own menu, it calls my code there is no
shortcut to that menu choice BUT alt+p prints and bypasses the code. Any
body got any other ideas to check.




david epsom dot com dot au said:
Alt P doesn't print ---- it calls the <underscore P>
menu item, which in view mode for a report happens to
be a print command. Make your own menu with your own
print command (or null action), or hide the file menu,
or ... something.

In the language of Access, [alt]p is an access key
(access as in accessibility), p is a shortcut key.

(david)


KB said:
One other one - what is the (is there a) symbol for the "alt" key? It seems
that an alt+p prints as well....



If you have a macro called Autokeys,
in which is a line were the MacroName value is ^p
and no action is set on that line,

then when you press ctrl+p nothing happens.

You may have to quit access to get the macro
to load/unload correctly.

You don't 'use' the macro at all. It just exists.
When MS developed Access, they used the macro's
to script the Access UI. (It was a long time ago).

The autokey setting doesn't prevent you from doing
anything to or with a report. It just intercepts
the scripted keystrokes.

(david)

Ok I give up. I want to stop users printing particular reports using
crtl+p
and alt+p. It's been suggested to me to use autokey macros. I
Click to expand...
rarely
if
ever
use macros so not really familiar with them. While I've tracked down
autokey
macros and can see how to create one it is not really obvious to
Click to expand...
me
how
I
might use it in a report. It's not a menu or toolbar and the
Click to expand...
report
has
no
print event. Anyone like to clear the way and suggest to me where the
light
is in this little brain teaser?

TIA

KB
Click to expand...
Click to expand...
Click to expand...
 
tried that - no go, you are right it's probably hard wired into Access? Even
tried a "cancel event" on the &p menu. No go. It appears that Microsoft
intends that user will be able to print a report regardless of the desires
of the designer of the database.



david epsom dot com dot au said:
hmmm. must be working even without menu. BUT can you
substitute your own P menu? Although my experience with
menu's with conflicting shortcut keys is that they never
seem to work properly.

(david)

KB said:
Made sure there is no menu shortcuts - there aren't now BUT alt+p *still*
prints so I'm stumped. I've got my own menu, it calls my code there is no
shortcut to that menu choice BUT alt+p prints and bypasses the code. Any
body got any other ideas to check.




david epsom dot com dot au said:
Alt P doesn't print ---- it calls the <underscore P>
menu item, which in view mode for a report happens to
be a print command. Make your own menu with your own
print command (or null action), or hide the file menu,
or ... something.

In the language of Access, [alt]p is an access key
(access as in accessibility), p is a shortcut key.

(david)


One other one - what is the (is there a) symbol for the "alt" key? It
seems
that an alt+p prints as well....



If you have a macro called Autokeys,
in which is a line were the MacroName value is ^p
and no action is set on that line,

then when you press ctrl+p nothing happens.

You may have to quit access to get the macro
to load/unload correctly.

You don't 'use' the macro at all. It just exists.
When MS developed Access, they used the macro's
to script the Access UI. (It was a long time ago).

The autokey setting doesn't prevent you from doing
anything to or with a report. It just intercepts
the scripted keystrokes.

(david)

Ok I give up. I want to stop users printing particular reports using
crtl+p
and alt+p. It's been suggested to me to use autokey macros. I rarely
if
ever
use macros so not really familiar with them. While I've tracked down
autokey
macros and can see how to create one it is not really obvious to me
how
I
might use it in a report. It's not a menu or toolbar and the report
has
no
print event. Anyone like to clear the way and suggest to me
Click to expand...
where
the
light
is in this little brain teaser?

TIA

KB
Click to expand...
Click to expand...
Click to expand...
 
Back
Top