I am experimenting with Access 2010 Runtime. Does anyone know how to get the
right click menu to work?

Right-click menus don't work in a runtime, unless you create your own.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access
Co-author: "Access Solutions", published by Wiley


"paii, Ron" <not (AT) none (DOT) org> wrote

"Arvin Meyer" <arvinm (AT) invalid (DOT) org> wrote

I was afraid of that. Does Access 2010 have a builder for right click menus?

?"paii, Ron" wrote in message
news:i9k52a$mtv$1 (AT) news (DOT) eternal-september.org...

No, but you can use macros as explained here:

How to do this is explained here:

http://office.microsoft.com/en-us/ac...CH100621911033

For cut + edit + paste, your macro look like:

Macro Name Action Command
Cut RunCommand Cut
Copy RunCommand Copy
Paste RunCommand Paste

Simply Save the above macro as MyMenu

Then create a macro that calls the above

eg:
Action Menu Name Menu Macro name Status Bar text
AddMenu MyRightClick MyMenu My Edit

save the above as mEdit

Then, in the forms property sheet, simply set the shortcut menu as mEdit

You can also use VBA code, such as outlined here:
http://support.microsoft.com/kb/209974


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

"Albert D. Kallal" <PleaseNOOOsPAMmkallal (AT) msn (DOT) com> wrote

Thank you Albert, I will look into those ASAP.

"Albert D. Kallal" <PleaseNOOOsPAMmkallal (AT) msn (DOT) com> wrote in
news:cmkvo.7761$4X5.4878 (AT) newsfe14 (DOT) iad:

That's just bloody awful. It's a step backwards to Access 2.

Idiots.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

?"David-W-Fenton" wrote in message
news:Xns9E16B8E5321DCf99a49ed1d0c49c5bbb2 (AT) 74 (DOT) 209.136.95...

The macro approach works in access 2003, perhaps even 2002.

I don't know when this ability was added, but it was NOT added in 2007, or
2010, but some version prior.

it just a possible option I suggested, and did not think it warranted the
name calling here as idiots,
and that is not a really productive response to the community here.

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

"Albert D. Kallal" <PleaseNOOOsPAMmkallal (AT) msn (DOT) com> wrote in
news:KQfwo.764$BM2.584 (AT) newsfe23 (DOT) iad:

???

The MS Access team is reverting functionality to something we
escaped almost 15 years ago, and that's not idiotic?

\/\/hatever, Albert.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

I found it easy to create a menu as a macro in Access 2007; run them in
a runtime environment, however, and it's a different matter - some items
work and others don't. Why?
Menu 1 - 4 RunCommands - Cut, Copy and Paste all work, but Spelling
won't. Why?
Menu 2 - Printout, Save and Close work fine, so why won't Sendobject
(as .pdf to email)? Why?

Some sites claim it's macros that are the problem, and to convert to
VBA. I thought that might work (if I could work out how to convert to
VBA!) until today.
Today, the database that works perfectly under Access, and was working
passably well in Runtime has decided to spit the dummy.
Screen 1 has 4 buttons, backed by macros. They all work.
Screen 2 has 5 buttons, all macro based, all working yesterday under
Runtime, now only three of which work and two of which bring up a series
of messages, basically saying "Computer says no".
Screen 3 was working brilliantly this morning - but this afternoon the
buttons have gone on strike in sympathy - but suddenly the EMAIL command
on the shortcut menu decides to WORK!
The gist of the messages was that something in a macro OR IN VBA
wouldn't work, and that nothing would work because some other undefined
action was going on. So if VBA won't work either, why waste my time
converting? And then it closes the program!
The result of all this is that whereas yesterday I could input data into
my database, now the only thing that happens is that it tells me it
won't work, and shuts down.



*** Sent via Developersdex http://www.developersdex.com ***

Aileen Hewat <msmerry (AT) netspace (DOT) net.au> wrote in
news:4cc91742$0$89392$815e3792 (AT) news (DOT) qwest.net:

It's very, very difficult to manage them, though, as macros are so
impossible to troubleshoot, and to untangle.

I speak from experience, having taken over an a 1996-era app last
year that had tons and tons of menus that were all macro-driven. It
was a nightmare to figure out what related to what. I ported
everything to code and toolbar menus because it's much easier to
manage (even though I knew it wasn't going to work really well with
the ribbon).

The Spell Checker is an Office component, and not distributable
(legally) as part of the runtime.

Not sure on that one.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/