Right Click in runtime
paii, Ron
right click menu to work?
Arvin Meyer
--
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" <n...@none.org> wrote in message
news:i9k2m1$dep$1...@news.eternal-september.org...
paii, Ron
"Arvin Meyer" <arv...@invalid.org> wrote in message
news:c6Wdnemlr5zHCSDR...@earthlink.com...
I was afraid of that. Does Access 2010 have a builder for right click menus?
Albert D. Kallal
news:i9k52a$mtv$1...@news.eternal-september.org...
>I was afraid of that. Does Access 2010 have a builder for right click
>menus?
No, but you can use macros as explained here:
How to do this is explained here:
http://office.microsoft.com/en-us/access/HA102825091033.aspx?pid=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
Pleasenos...@msn.com
paii, Ron
"Albert D. Kallal" <PleaseNOOO...@msn.com> wrote in message
news:cmkvo.7761$4X5....@newsfe14.iad...
Thank you Albert, I will look into those ASAP.
David-W-Fenton
> ?"paii, Ron" wrote in message
> news:i9k52a$mtv$1...@news.eternal-september.org...
>
>>I was afraid of that. Does Access 2010 have a builder for right
>>click menus?
>
> No, but you can use macros as explained here:
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/
Albert D. Kallal
news:Xns9E16B8E5321DCf9...@74.209.136.95...
>> No, but you can use macros as explained here:
>That's just bloody awful. It's a step backwards to Access 2.
>Idiots.
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.
David-W-Fenton
> ?"David-W-Fenton" wrote in message
> news:Xns9E16B8E5321DCf9...@74.209.136.95...
>
>>> No, but you can use macros as explained here:
>
>>That's just bloody awful. It's a step backwards to Access 2.
>
>>Idiots.
>
> 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.
???
The MS Access team is reverting functionality to something we
escaped almost 15 years ago, and that's not idiotic?
\/\/hatever, Albert.
Aileen Hewat
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 ***
David-W-Fenton
news:4cc91742$0$89392$815e...@news.qwest.net:
> I found it easy to create a menu as a macro in Access 2007;
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).
> 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?
The Spell Checker is an Office component, and not distributable
(legally) as part of the runtime.
> Menu 2 - Printout, Save and Close work fine, so why won't
> Sendobject (as .pdf to email)? Why?
Not sure on that one.
ellen tuck
I found instructions for converting macros to VBA - easy when someone
tells you how
(http://www.aspfree.com/c/a/Microsoft-Access/Jump-Start-VBA-Skills-with-
MS-Access-Macros/). So I did. All went well until I tried converting
an Addmenu macro - no equivalent in VBA. So, if it can't be converted,
how can it activate the menu?
As for the SpellChecker, the computer with Runtime has all the other
Office components; don't tell me they all have separate SpellCheckers.
Nobody could be that stupid.
Further to yesterday's meltdown:-
Originally, not knowing how to link FE/BE under Runtime, I combined them
and the majority of macros worked, with the exception of SpellChecker
and Email.
Following advice, I placed the BE at C:\Program
Files\(Mydatabase\database)on my computer, created the links, then
replicated that on the Runtime computer. My logic says that should
work.
I was able to view data in a form, e.g., an invoice, but could not add a
new one. I could even view an existing Invoice for printout, and
magically, the email button worked! But I could not open popup forms - I
got a series of messages, including the one that told me the problems
lay in macro or VBA, or because something was trying to run in the
background. Now my logic fails me.
Does anyone have any suggestions?
Thanks
Elllentuck
David-W-Fenton
news:4cca01a2$0$89879$815e...@news.qwest.net:
> I found instructions for converting macros to VBA - easy when
> someone tells you how
> (http://www.aspfree.com/c/a/Microsoft-Access/Jump-Start-VBA-Skills-
> with- MS-Access-Macros/). So I did. All went well until I tried
> converting an Addmenu macro - no equivalent in VBA. So, if it
> can't be converted, how can it activate the menu?
Those have to be replaced with toolbars, but if you're looking for
compatibility with the ribbon, you have to keep them.
> As for the SpellChecker, the computer with Runtime has all the
> other Office components; don't tell me they all have separate
> SpellCheckers. Nobody could be that stupid.
I don't know that it's a matter of it being installed or not, but
that the runtime is specifically designed to not be able to use it.
I don't know the exact details. I've deployed very few runtime apps,
and have utilized the spellchecker only once in any of my apps.
> Further to yesterday's meltdown:-
> Originally, not knowing how to link FE/BE under Runtime, I
> combined them and the majority of macros worked, with the
> exception of SpellChecker and Email.
> Following advice, I placed the BE at C:\Program
> Files\(Mydatabase\database)on my computer, created the links, then
> replicated that on the Runtime computer. My logic says that
> should work.
> I was able to view data in a form, e.g., an invoice, but could not
> add a new one. I could even view an existing Invoice for
> printout, and magically, the email button worked! But I could not
> open popup forms - I got a series of messages, including the one
> that told me the problems lay in macro or VBA, or because
> something was trying to run in the background. Now my logic fails
> me.
>
> Does anyone have any suggestions?
It's really difficult to troubleshoot macros, which is one of the
reasons I avoid them like the plague.
paii, Ron
> other Office components; don't tell me they all have separate
> SpellCheckers. Nobody could be that stupid.
Runtime spell check with F7 does not work with runtime, but adding "Spell
Check" to the ribbon does.
Assuming Office 2010 is installed.