On Feb 17, 7:28 pm, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
Hi Wayne
The disppearing Close button (and max and min) from the Preview ribbon is a
bug. We have it listed here:
http://allenbrowne.com/Access2007.html#Bugs
The switch from menus and toolbars to ribbon is a major change that causes
initial consternation for most users. Ultimately it means you will need to
redevelop your custom menus/toolbars as ribbons. Custom ribbons are not as
easy as custom menus/toolbars, so there's a learning curve on that. The end
of the article linked above has some links, including AccessRibbon.com.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Wayne" <cqdigi...@volcanomail.comwrote in message
news:11**********************@p10g2000cwp.googlegr oups.com...
I've been having a click around Access 2007 this afternoon and have
discovered some things that range from annoying to alarming. My
Access 2003 menu bars, which I, like many others, use extensively, are
now hidden behind an "Add Ins" tab on the Ribbon. Hardly an intuitive
place for a user to find them. Unless my memory is failing me, I'm
sure that Access 2003 menus displayed normally in the 2007 Beta.
The other thing I've discovered which seems to be a bug is that when
reports are opened in Print Preview mode and maximized with code when
they open, sometimes the minimize, size and close buttons don't appear
on the ribbon. I should add that I have the Ribbon minimized with
only the "tab" section showing. By "sometimes" I mean that it seems to
be a hit and miss affair, with some reports showing the buttons and
others not showing them. There is nothing inherently different about
the reports or how they are opened. The only way to close the report
is the absence of the buttons is to expand the Ribbon and press "Close
Print Preview". I'd be interested to know if anyone else is
experiencing this.
I'm also interested to know what others think about the potential
rework of existing applications that is going to be caused by the
Ribbon. I haven't seen that anyone has come up with a way of hiding
it yet, and the fact that custom menu bars are hidden behind the "Add
Ins" tab is surely going to cause some grief.- Hide quoted text -
- Show quoted text -
Thanks for the reply Allen. What concerns me about the ribbon is the
amount of screen real estate it consumes, in my case for no good
purpose. Most of my applications have a few custom menu bars that are
usually specific to particular forms and reports. None of these menu
bars contain more than a few buttons on the bar itself and a short
menu or two. Putting these few items on the ribbon seems like a gross
waste of space. I'd be interested to know if others will go anywhere
near filling a Ribbon with their applications.
I'm not sure if the ribbon can be customised to change its contents
depending on which form or report is displayed as I am doing with my
custom menu bars now - if not the functionality would be severely
limited for my purposes. I've created a blank Ribbon which only shows
the "tab" section of the ribbon by using code from here:
http://msdn2.microsoft.com/en-us/library/bb187398.aspx. This would be
one way of reclaiming most of the real estate that the ribbon
consumes, but only when the bug is fixed that makes my report buttons
disappear. Creating this blank Ribbon or a custom Ribbon with buttons
on it also seems to have the effect of preventing changes to the Quick
Access Bar. I'm not sure if this is by design, but it is a plus if
one doesn't want users adding buttons to the bar.
Since my first post I've noticed that I can nominate a particular
startup custom menu bar from my Access 2003 application and Access
2007 will treat my custom menus the same as 2003 with no Ribbon as a
bonus.
On another subject, the sooner someone figures out how to make Access
2003 and 2007 coexist peacefully the better off everyone will be. As
you have noted elsewhere they each want to reinstall after the other
has been used. Surely MS foresaw that some people would want to run
both versions and could have allowed for this. On my machine 2000 and
2003 live happily together so why not 2007 as well? I can only
wonder.