Prev: xlFillDefault, based on values in ColA to ColZ
Next: Data aggregation with multiple workbooks
From: Dave Peterson on 11 May 2010 07:59
Help service????

And who knows about the summit (or MVP-hood) nowadays???

Bob Phillips wrote:

> You mean you don't run that help service any more? I didn't know that.
>
> So you must have time to attend the summit now?
>
> Bob
>
> "Dave Peterson" <petersod(a)XSPAMverizon.net> wrote in message
> news:e6yRHnI8KHA.1316(a)TK2MSFTNGP02.phx.gbl...
>
>>Or just retired with nothing better to do!
>>
>>
>>
>>Bob Phillips wrote:
>>
>>
>>>"Dave Peterson" <petersod(a)XSPAMverizon.net> wrote in message
>>>news:uODR9sG8KHA.5808(a)TK2MSFTNGP02.phx.gbl...
>>>
>>>
>>>
>>>>You shared that info to another post. So I figured I'd just add it into
>>>>one of my "saved from a previous post" replies.
>>>
>>>
>>>
>>>That is what I mean, you see everything. I think there are lots of you in
>>>reality, Dave Peterson is really a franchise <ebg>
>>
>>--
>>
>>Dave Peterson
>
>
>

--

Dave Peterson
From: JD McLeod on 11 May 2010 21:25
Thanks GS. Not that it matters, but why the change in Excel 2007? It seemed
so easy for us "novice" users to create custom menus in the earlier version.
It seems very much more complicated now. Anyway, I read where i will need to
download RibbonX in order to create the add-in menus i need. Will other
users of the add-in have to also download RibbonX or is that just for
developing the add-ins? Thanks.

"GS" wrote:

> JD McLeod brought next idea :
> > I am new to Excel 2007 and have two questions. 1. In previous versions, i
> > was able to create a custom menu bar as a drop down from the top menu and add
> > macros to it. I could do all of this without having to go in and write code.
> > Now in 2007, i see how to add a menu bar to the quick access tool bar, but i
> > can't figure out how to assign macros to that menu bar. Any ideas? 2. How
> > do you go about creating an add-in that other users could add to their
> > computer and use? I have never done this before and wanted to know if that
> > is a good way to share a custom menu bar or tool bar?
> > Thanks.
>
> Yes, creating an addi is probably the easiest approach because you can
> control and maintain the macros in a common toolbar rather than having
> to get users to update their custom menus. The menus/toolbar will
> appear on the Addins tab of the ribbon.
>
> How To:
> Put your code in a workbook saved as an addin (.xla). Include code to
> build the toolbar and manage it between sessions so it creates itself
> on startup and removes itself on shutdown. Do your programming in the
> earliest version of Excel you expect users to have.
>
> Books I recommend:
> Excel <version> Power Programming with VBA
> by John Walkenbach
>
> Excel <version> VBA Programmer's Reference
> by Bovey, Bullen, Green
>
> Additionally, there are many people here in this NG that will help you
> along the way!
>
> regards,
> Garry
>
>
> .
>
From: GS on 11 May 2010 22:40
JD McLeod used his keyboard to write :
> Thanks GS. Not that it matters, but why the change in Excel 2007? It seemed
> so easy for us "novice" users to create custom menus in the earlier version.
> It seems very much more complicated now. Anyway, I read where i will need to
> download RibbonX in order to create the add-in menus i need. Will other
> users of the add-in have to also download RibbonX or is that just for
> developing the add-ins? Thanks.

RibbonX is part of Excel. You just need to download the viewer (Custom
UI Editor for MS Office) to allow you to edit the XML that is used to
modify the ribbon. I recommend you follow Dave's links. Bob Phillip's
article is one of the best I've seen on the web so far. Ron de Brun has
some good xlsm samples on his site as well. I don't use workbook-based
addins much anymore but yes, your addin will set up the ribbon for
anyone who uses it.

As for why M$ changed things goes, the answer is in their second
initial! It definitely complicates programming more than it needs to
be, though. That's partly why I stopped using workbook addins. Problem
I see here is that the next workbook opened that changes the ribbon
puts your addin in the back seat until it closes. I suspect Excel
toggles settings according to which workbook is active but that
scenario doesn't appeal to me at all. Most all my addins are
task-specific apps that I prefer to run as dictator apps in their own
instance of Excel. That way I can hide the default ribbon tabs and use
my own menus/toolbars by ensuring the Addins tab is the only one
available. This can be done with workbook addins too but many of my
clients are overly security cautious and so I use VB6 COMAddins.
Fortunately, this is the only case where the XML can be passed via
code. Otherwise, I'd need to use a dummy xlsm to set up my UI. Way too
much hooplah for me! Besides, the Addins tab supports using our earlier
version menus and toolbars so why try to fix what ain't broke? Most my
addins use a table-driven system for creating menus/toolbars and so I
use the same xla to do that and have all menus use a common procedure
(as in the sample in Bob's article) to pass the OnAction (in the Tag
prop) and any parameters (in the Parameter prop) to the COMAddin. Bob's
example uses the 'Run' method to execute his procs in the xla. My
COMAddin uses the 'CallByName' function to do the same thing,
respectively.

Yep, the ribbon sure has brought a lot of hassles into the picture.
Nice thing about my approach is 'no ribbon, no hassles'! I totally lock
down Excel so the user only has access to features and functionality
required to use my app. That completely removes any distractions caused
by the Excel UI that isn't being used. It also allows me to prevent
opening workbooks that don't belong to my app. Fact is, some of my
clients don't even realize they're using Excel!

Anyway, follow those links and you'll have results you can smile about.

regards,
Garry


From: JD McLeod on 12 May 2010 00:04
One last question on this topic before I begin. I am able to add commands to
the "quick acces toolbar" such as Menu Commands and Toolbar Commands. When i
click on them, they drop down as if they should have more choices on them to
select from. This resembles the old style of custom menus. How do you or
can you add additional items to these menus. I found them by selecting "More
Commands" from the quick access tool bar and they were under the Add-ins
section. Thanks.

"GS" wrote:

> JD McLeod used his keyboard to write :
> > Thanks GS. Not that it matters, but why the change in Excel 2007? It seemed
> > so easy for us "novice" users to create custom menus in the earlier version.
> > It seems very much more complicated now. Anyway, I read where i will need to
> > download RibbonX in order to create the add-in menus i need. Will other
> > users of the add-in have to also download RibbonX or is that just for
> > developing the add-ins? Thanks.
>
> RibbonX is part of Excel. You just need to download the viewer (Custom
> UI Editor for MS Office) to allow you to edit the XML that is used to
> modify the ribbon. I recommend you follow Dave's links. Bob Phillip's
> article is one of the best I've seen on the web so far. Ron de Brun has
> some good xlsm samples on his site as well. I don't use workbook-based
> addins much anymore but yes, your addin will set up the ribbon for
> anyone who uses it.
>
> As for why M$ changed things goes, the answer is in their second
> initial! It definitely complicates programming more than it needs to
> be, though. That's partly why I stopped using workbook addins. Problem
> I see here is that the next workbook opened that changes the ribbon
> puts your addin in the back seat until it closes. I suspect Excel
> toggles settings according to which workbook is active but that
> scenario doesn't appeal to me at all. Most all my addins are
> task-specific apps that I prefer to run as dictator apps in their own
> instance of Excel. That way I can hide the default ribbon tabs and use
> my own menus/toolbars by ensuring the Addins tab is the only one
> available. This can be done with workbook addins too but many of my
> clients are overly security cautious and so I use VB6 COMAddins.
> Fortunately, this is the only case where the XML can be passed via
> code. Otherwise, I'd need to use a dummy xlsm to set up my UI. Way too
> much hooplah for me! Besides, the Addins tab supports using our earlier
> version menus and toolbars so why try to fix what ain't broke? Most my
> addins use a table-driven system for creating menus/toolbars and so I
> use the same xla to do that and have all menus use a common procedure
> (as in the sample in Bob's article) to pass the OnAction (in the Tag
> prop) and any parameters (in the Parameter prop) to the COMAddin. Bob's
> example uses the 'Run' method to execute his procs in the xla. My
> COMAddin uses the 'CallByName' function to do the same thing,
> respectively.
>
> Yep, the ribbon sure has brought a lot of hassles into the picture.
> Nice thing about my approach is 'no ribbon, no hassles'! I totally lock
> down Excel so the user only has access to features and functionality
> required to use my app. That completely removes any distractions caused
> by the Excel UI that isn't being used. It also allows me to prevent
> opening workbooks that don't belong to my app. Fact is, some of my
> clients don't even realize they're using Excel!
>
> Anyway, follow those links and you'll have results you can smile about.
>
> regards,
> Garry
>
>
> .
>
From: GS on 12 May 2010 02:59
JD McLeod presented the following explanation :
> One last question on this topic before I begin. I am able to add commands to
> the "quick acces toolbar" such as Menu Commands and Toolbar Commands. When i
> click on them, they drop down as if they should have more choices on them to
> select from. This resembles the old style of custom menus. How do you or
> can you add additional items to these menus. I found them by selecting "More
> Commands" from the quick access tool bar and they were under the Add-ins
> section. Thanks.

I'm sorry but I've never had reason to use that feature and so I can't
help you with it. Hopefully someone else will pick it up and run with
it. I'm sure I could look it up somewhere, but there's probably lots
more folks here better able to address this than I would be able to in
the short term.

Since this can also be done via the UI, try recording a macro and going
through the steps to see if it generates any code.

Garry
--

>
> "GS" wrote:
>
>> JD McLeod used his keyboard to write :
>>> Thanks GS. Not that it matters, but why the change in Excel 2007? It
>>> seemed so easy for us "novice" users to create custom menus in the earlier
>>> version. It seems very much more complicated now. Anyway, I read where i
>>> will need to download RibbonX in order to create the add-in menus i need.
>>> Will other users of the add-in have to also download RibbonX or is that
>>> just for developing the add-ins? Thanks.
>>
>> RibbonX is part of Excel. You just need to download the viewer (Custom
>> UI Editor for MS Office) to allow you to edit the XML that is used to
>> modify the ribbon. I recommend you follow Dave's links. Bob Phillip's
>> article is one of the best I've seen on the web so far. Ron de Brun has
>> some good xlsm samples on his site as well. I don't use workbook-based
>> addins much anymore but yes, your addin will set up the ribbon for
>> anyone who uses it.
>>
>> As for why M$ changed things goes, the answer is in their second
>> initial! It definitely complicates programming more than it needs to
>> be, though. That's partly why I stopped using workbook addins. Problem
>> I see here is that the next workbook opened that changes the ribbon
>> puts your addin in the back seat until it closes. I suspect Excel
>> toggles settings according to which workbook is active but that
>> scenario doesn't appeal to me at all. Most all my addins are
>> task-specific apps that I prefer to run as dictator apps in their own
>> instance of Excel. That way I can hide the default ribbon tabs and use
>> my own menus/toolbars by ensuring the Addins tab is the only one
>> available. This can be done with workbook addins too but many of my
>> clients are overly security cautious and so I use VB6 COMAddins.
>> Fortunately, this is the only case where the XML can be passed via
>> code. Otherwise, I'd need to use a dummy xlsm to set up my UI. Way too
>> much hooplah for me! Besides, the Addins tab supports using our earlier
>> version menus and toolbars so why try to fix what ain't broke? Most my
>> addins use a table-driven system for creating menus/toolbars and so I
>> use the same xla to do that and have all menus use a common procedure
>> (as in the sample in Bob's article) to pass the OnAction (in the Tag
>> prop) and any parameters (in the Parameter prop) to the COMAddin. Bob's
>> example uses the 'Run' method to execute his procs in the xla. My
>> COMAddin uses the 'CallByName' function to do the same thing,
>> respectively.
>>
>> Yep, the ribbon sure has brought a lot of hassles into the picture.
>> Nice thing about my approach is 'no ribbon, no hassles'! I totally lock
>> down Excel so the user only has access to features and functionality
>> required to use my app. That completely removes any distractions caused
>> by the Excel UI that isn't being used. It also allows me to prevent
>> opening workbooks that don't belong to my app. Fact is, some of my
>> clients don't even realize they're using Excel!
>>
>> Anyway, follow those links and you'll have results you can smile about.
>>
>> regards,
>> Garry
>>
>>
>> .
>>


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: xlFillDefault, based on values in ColA to ColZ
Next: Data aggregation with multiple workbooks