[AccessD] ...table driven command/menu bar interface needed

jc/rocky

...afaik the office 12/14 object models no longer let you build commandbar 
menus from the developer interface ...you have to do it through vba ...as 
for 2010, it appears there is now LIMITED customization of the ribbon 
interface available that will allow us to achieve "something" similar to the 
commandbars ...so if I go that route, turning the ribbon off isn't an option 
...it appears that the minimum I can achieve through that is a two row 
interface, one for the tabs and one for the commands ...and there appear to 
be severe limitations on the command flexibility ...right now, I'm 
testing/debugging a table driven command bar menu builder that should work 
in both A2k3 and A2010 ...we'll see if it works ...but then I'm afraid 
they'll deprecate the whole command bar object in the next version ...the 
@#$%^&%^'s running Office Development appear to have their careers invested 
in the ribbon and the Access Development team are having to walk carefully 
around it ...now I'm faced with an entire user interface built around the 32 
bit MSCOMMctl.ocx treeview that simply won't work in Office 2010 64bit 
because MS refuses to upgrade the common controls to 64bit.

...am I feeling a bit pissed on? ...you bet, like a tree root in a dog park!

William

--------------------------------------------------
From: "Rocky Smolin" <rockysmolin at bchacc.com>
Sent: Monday, May 10, 2010 9:07 AM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] ...table driven command/menu bar interface needed

> In a rather complex app for a patent attorney  with lots of forms, and 
> which
> has to run on both 2003 and 2007, I just check for the version turn off 
> the
> ribbon and navigation pane if it's 2007. Ribbon problem solved.
>
> R
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Monday, May 10, 2010 5:35 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] ...table driven command/menu bar interface needed
>
> >>>...I'm wondering when the idiots behind the ribbon fiasco in Office 
> >>>will
> finally get the fact that a LOT of people DON"T have 2400x1600 screens,
> including millions of notebook users ...will it be before or after a
> critical mass decide to move beyond Office?
>
> ROTFL!
>
> William... what you don't like the fact that all of your applications
> suddenly have vertical sliders because the ribbon is waaaaaaaaaaaaaaay 
> more
> important than your actual APPLICATION?  I mean... the ribbon IS the
> application right?  All that fun stuff that the user of the application 
> has
> no business ever doing IS THE APPLICATION RIGHT?
>
> Get with the program man!  REDESIGN all of your applications to give
> Microsoft their silly ribbon!
> And then inform your users (politely) that if you ever catch them using 
> any
> of that stuff they aren't supposed to even have access to that you will 
> cut
> off the hand at the wrist, with a white hot sword (cauterizes the wound 
> and
> stops the bleeding).
>
> Who are we to tell the 800 pound gorilla that they can't mutilate millions
> of existing applications?
>  Far far better to mutilate our users IMHO.
>
> John W. Colby
> www.ColbyConsulting.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>